1. 程式人生 > >SpringMVC實現原理及詳解

SpringMVC實現原理及詳解

1、Spring mvc介紹

SpringMVC框架是以請求為驅動,圍繞Servlet設計,將請求發給控制器,然後通過模型物件,分派器來展示請求結果檢視。其中核心類是DispatcherServlet,它是一個Servlet,頂層是實現的Servlet介面。

 

2、SpringMVC使用

需要在web.xml中配置DispatcherServlet。並且需要配置spring監聽器ContextLoaderListener

 
  1.         <listener

    >

  2.             <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>

  3.         </listener>       

  4.         <servlet

    >

  5. <servlet-name>springmvc</servlet-name>

  6. <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>

  7.                 <!-- 如果不設定init-param標籤,則必須在/WEB-INF/下建立xxx-servlet.xml檔案,其中xxx是servlet-name中配置的名稱。 -->

  8.                 <init-param>

  9. <param-name>contextConfigLocation</param-name>

  10. <param-value>classpath:spring/springmvc-servlet.xml</param-value>

  11. </init-param>

  12. <load-on-startup>1</load-on-startup>

  13. </servlet>

  14. <servlet-mapping>

  15. <servlet-name>springmvc</servlet-name>

  16. <url-pattern>/</url-pattern>

  17. </servlet-mapping>

3、SpringMVC執行原理

如圖所示:

流程說明:

(1)客戶端(瀏覽器)傳送請求,直接請求到DispatcherServlet。

(2)DispatcherServlet根據請求資訊呼叫HandlerMapping,解析請求對應的Handler。

(3)解析到對應的Handler後,開始由HandlerAdapter介面卡處理。

(4)HandlerAdapter會根據Handler來呼叫真正的處理器開處理請求,並處理相應的業務邏輯。

(5)處理器處理完業務後,會返回一個ModelAndView物件,Model是返回的資料物件,View是個邏輯上的View。

(6)ViewResolver會根據邏輯View查詢實際的View。

(7)DispaterServlet把返回的Model傳給View。

(8)通過View返回給請求者(瀏覽器)

4、DispatcherServlet詳細解析

首先看下原始碼:

 
  1. package org.springframework.web.servlet;

  2.  
  3. @SuppressWarnings("serial")

  4. public class DispatcherServlet extends FrameworkServlet {

  5.  
  6. public static final String MULTIPART_RESOLVER_BEAN_NAME = "multipartResolver";

  7. public static final String LOCALE_RESOLVER_BEAN_NAME = "localeResolver";

  8. public static final String THEME_RESOLVER_BEAN_NAME = "themeResolver";

  9. public static final String HANDLER_MAPPING_BEAN_NAME = "handlerMapping";

  10. public static final String HANDLER_ADAPTER_BEAN_NAME = "handlerAdapter";

  11. public static final String HANDLER_EXCEPTION_RESOLVER_BEAN_NAME = "handlerExceptionResolver";

  12. public static final String REQUEST_TO_VIEW_NAME_TRANSLATOR_BEAN_NAME = "viewNameTranslator";

  13. public static final String VIEW_RESOLVER_BEAN_NAME = "viewResolver";

  14. public static final String FLASH_MAP_MANAGER_BEAN_NAME = "flashMapManager";

  15. public static final String WEB_APPLICATION_CONTEXT_ATTRIBUTE = DispatcherServlet.class.getName() + ".CONTEXT";

  16. public static final String LOCALE_RESOLVER_ATTRIBUTE = DispatcherServlet.class.getName() + ".LOCALE_RESOLVER";

  17. public static final String THEME_RESOLVER_ATTRIBUTE = DispatcherServlet.class.getName() + ".THEME_RESOLVER";

  18. public static final String THEME_SOURCE_ATTRIBUTE = DispatcherServlet.class.getName() + ".THEME_SOURCE";

  19. public static final String INPUT_FLASH_MAP_ATTRIBUTE = DispatcherServlet.class.getName() + ".INPUT_FLASH_MAP";

  20. public static final String OUTPUT_FLASH_MAP_ATTRIBUTE = DispatcherServlet.class.getName() + ".OUTPUT_FLASH_MAP";

  21. public static final String FLASH_MAP_MANAGER_ATTRIBUTE = DispatcherServlet.class.getName() + ".FLASH_MAP_MANAGER";

  22. public static final String EXCEPTION_ATTRIBUTE = DispatcherServlet.class.getName() + ".EXCEPTION";

  23. public static final String PAGE_NOT_FOUND_LOG_CATEGORY = "org.springframework.web.servlet.PageNotFound";

  24. private static final String DEFAULT_STRATEGIES_PATH = "DispatcherServlet.properties";

  25. protected static final Log pageNotFoundLogger = LogFactory.getLog(PAGE_NOT_FOUND_LOG_CATEGORY);

  26. private static final Properties defaultStrategies;

  27. static {

  28. try {

  29. ClassPathResource resource = new ClassPathResource(DEFAULT_STRATEGIES_PATH, DispatcherServlet.class);

  30. defaultStrategies = PropertiesLoaderUtils.loadProperties(resource);

  31. }

  32. catch (IOException ex) {

  33. throw new IllegalStateException("Could not load 'DispatcherServlet.properties': " + ex.getMessage());

  34. }

  35. }

  36.  
  37. /** Detect all HandlerMappings or just expect "handlerMapping" bean? */

  38. private boolean detectAllHandlerMappings = true;

  39.  
  40. /** Detect all HandlerAdapters or just expect "handlerAdapter" bean? */

  41. private boolean detectAllHandlerAdapters = true;

  42.  
  43. /** Detect all HandlerExceptionResolvers or just expect "handlerExceptionResolver" bean? */

  44. private boolean detectAllHandlerExceptionResolvers = true;

  45.  
  46. /** Detect all ViewResolvers or just expect "viewResolver" bean? */

  47. private boolean detectAllViewResolvers = true;

  48.  
  49. /** Throw a NoHandlerFoundException if no Handler was found to process this request? **/

  50. private boolean throwExceptionIfNoHandlerFound = false;

  51.  
  52. /** Perform cleanup of request attributes after include request? */

  53. private boolean cleanupAfterInclude = true;

  54.  
  55. /** MultipartResolver used by this servlet */

  56. private MultipartResolver multipartResolver;

  57.  
  58. /** LocaleResolver used by this servlet */

  59. private LocaleResolver localeResolver;

  60.  
  61. /** ThemeResolver used by this servlet */

  62. private ThemeResolver themeResolver;

  63.  
  64. /** List of HandlerMappings used by this servlet */

  65. private List<HandlerMapping> handlerMappings;

  66.  
  67. /** List of HandlerAdapters used by this servlet */

  68. private List<HandlerAdapter> handlerAdapters;

  69.  
  70. /** List of HandlerExceptionResolvers used by this servlet */

  71. private List<HandlerExceptionResolver> handlerExceptionResolvers;

  72.  
  73. /** RequestToViewNameTranslator used by this servlet */

  74. private RequestToViewNameTranslator viewNameTranslator;

  75.  
  76. private FlashMapManager flashMapManager;

  77.  
  78. /** List of ViewResolvers used by this servlet */

  79. private List<ViewResolver> viewResolvers;

  80.  
  81. public DispatcherServlet() {

  82. super();

  83. }

  84.  
  85. public DispatcherServlet(WebApplicationContext webApplicationContext) {

  86. super(webApplicationContext);

  87. }

  88.  
  89. @Override

  90. protected void onRefresh(ApplicationContext context) {

  91. initStrategies(context);

  92. }

  93.  
  94. protected void initStrategies(ApplicationContext context) {

  95. initMultipartResolver(context);

  96. initLocaleResolver(context);

  97. initThemeResolver(context);

  98. initHandlerMappings(context);

  99. initHandlerAdapters(context);

  100. initHandlerExceptionResolvers(context);

  101. initRequestToViewNameTranslator(context);

  102. initViewResolvers(context);

  103. initFlashMapManager(context);

  104. }

  105. }

DispatcherServlet類中的屬性beans:

HandlerMapping:用於handlers對映請求和一系列的對於攔截器的前處理和後處理,大部分用@Controller註解。

HandlerAdapter:幫助DispatcherServlet處理對映請求處理程式的介面卡,而不用考慮實際呼叫的是 哪個處理程式。

HandlerExceptionResolver:處理對映異常。

ViewResolver:根據實際配置解析實際的View型別。

LocaleResolver:解決客戶正在使用的區域設定以及可能的時區,以便能夠提供國際化視野。

ThemeResolver:解決Web應用程式可以使用的主題,例如提供個性化佈局。

MultipartResolver:解析多部分請求,以支援從HTML表單上傳檔案。

FlashMapManager:儲存並檢索可用於將一個請求屬性傳遞到另一個請求的input和output的FlashMap,通常用於重定向。

在Web MVC框架中,每個DispatcherServlet都擁自己的WebApplicationContext,它繼承了ApplicationContext。WebApplicationContext包含了其上下文和Servlet例項之間共享的所有的基礎框架beans。

 

  • HandlerMapping:

HandlerMapping介面處理請求的對映

HandlerMapping介面的實現類:

SimpleUrlHandlerMapping類通過配置檔案把URL對映到Controller類。

DefaultAnnotationHandlerMapping類通過註解把URL對映到Controller類。

 

  • HandlerAdapter:

HandlerAdapter介面-處理請求對映

AnnotationMethodHandlerAdapter:通過註解,把請求URL對映到Controller類的方法上。

  • HandlerExceptionResolver

HandlerExceptionResolver介面-異常處理介面

SimpleMappingExceptionResolver通過配置檔案進行異常處理。

AnnotationMethodHandlerExceptionResolver:通過註解進行異常處理。

  • ViewResolver:

ViewResolver介面解析View檢視。

UrlBasedViewResolver類 通過配置檔案,把一個檢視名交給到一個View來處理。

 

參考資料:http://elf8848.iteye.com/blog/875830

裝載於:https://blog.csdn.net/yanweihpu/article/details/80366218