Java從源碼角度解析SpringMVC執(zhí)行流程
SpringMVC執(zhí)行流程在面試中經(jīng)常會(huì)被問(wèn)到,本篇文章通過(guò)源碼的方式簡(jiǎn)單的了解一下SpringMVC執(zhí)行流程。
先看流程
先看一下SpringMVC執(zhí)行流程再看源碼,有助理解:
- ?戶發(fā)送請(qǐng)求?前端控制器DispatcherServlet。
- DispatcherServlet 收到請(qǐng)求調(diào)? HandlerMapping 處理器映射器。
- 處理器映射器找到具體的處理器(可以根據(jù)xml配置、注解進(jìn)?查找),?成處理器及處理器攔截器(如果有則?成)?并返回給DispatcherServlet。
- DispatcherServlet調(diào)?HandlerAdapter處理器適配器。
- HandlerAdapter經(jīng)過(guò)適配調(diào)?具體的處理器(Controller,也叫后端控制器)
- Controller執(zhí)?完成返回ModelAndView。
- HandlerAdapter 將 Controller 執(zhí)?結(jié)果 ModelAndView 返回給DispatcherServlet。
- DispatcherServlet將ModelAndView傳給ViewReslover視圖解析器。
- ViewReslover解析后返回具體View。
- DispatcherServlet根據(jù)View進(jìn)?渲染視圖(即將模型數(shù)據(jù)填充?視圖中)。
- DispatcherServlet 響應(yīng)?戶。
再看源碼
我們都知道當(dāng)從用戶發(fā)起請(qǐng)求到后端是,首先走的就是DispatcherServlet,接著就會(huì)調(diào)用doService()
方法執(zhí)行業(yè)務(wù)邏輯,doService()
方法也只是一個(gè)中轉(zhuǎn)站,實(shí)際執(zhí)行邏輯的是doDispatch()
方法,且看源碼:
@Override protected void doService(HttpServletRequest request, HttpServletResponse response) throws Exception { logRequest(request); // 省略部分源碼 try { // 執(zhí)行實(shí)際邏輯 doDispatch(request, response); } finally { if (!WebAsyncUtils.getAsyncManager(request).isConcurrentHandlingStarted()) { // Restore the original attribute snapshot, in case of an include. if (attributesSnapshot != null) { restoreAttributesAfterInclude(request, attributesSnapshot); } } ServletRequestPathUtils.setParsedRequestPath(previousRequestPath, request); } }
doDispatch 方法:
protected void doDispatch(HttpServletRequest request, HttpServletResponse response) throws Exception { HttpServletRequest processedRequest = request; HandlerExecutionChain mappedHandler = null; boolean multipartRequestParsed = false; WebAsyncManager asyncManager = WebAsyncUtils.getAsyncManager(request); try { ModelAndView mv = null; Exception dispatchException = null; try { processedRequest = checkMultipart(request); multipartRequestParsed = (processedRequest != request); // 為當(dāng)前請(qǐng)求獲取映射處理器 mappedHandler = getHandler(processedRequest); if (mappedHandler == null) { noHandlerFound(processedRequest, response); return; } // 獲取映射處理器適配器 HandlerAdapter ha = getHandlerAdapter(mappedHandler.getHandler()); // Process last-modified header, if supported by the handler. String method = request.getMethod(); boolean isGet = "GET".equals(method); if (isGet || "HEAD".equals(method)) { long lastModified = ha.getLastModified(request, mappedHandler.getHandler()); if (new ServletWebRequest(request, response).checkNotModified(lastModified) && isGet) { return; } } if (!mappedHandler.applyPreHandle(processedRequest, response)) { return; } // 實(shí)際調(diào)用的Handler mv = ha.handle(processedRequest, response, mappedHandler.getHandler()); if (asyncManager.isConcurrentHandlingStarted()) { return; } applyDefaultViewName(processedRequest, mv); mappedHandler.applyPostHandle(processedRequest, response, mv); } catch (Exception ex) { dispatchException = ex; } catch (Throwable err) { // As of 4.3, we're processing Errors thrown from handler methods as well, // making them available for @ExceptionHandler methods and other scenarios. dispatchException = new NestedServletException("Handler dispatch failed", err); } //處理轉(zhuǎn)發(fā)結(jié)果 processDispatchResult(processedRequest, response, mappedHandler, mv, dispatchException); } catch (Exception ex) { triggerAfterCompletion(processedRequest, response, mappedHandler, ex); } catch (Throwable err) { triggerAfterCompletion(processedRequest, response, mappedHandler, new NestedServletException("Handler processing failed", err)); } finally { if (asyncManager.isConcurrentHandlingStarted()) { // Instead of postHandle and afterCompletion if (mappedHandler != null) { mappedHandler.applyAfterConcurrentHandlingStarted(processedRequest, response); } } else { // Clean up any resources used by a multipart request. if (multipartRequestParsed) { cleanupMultipart(processedRequest); } } } }
下面來(lái)看一下其中幾個(gè)重要的方法:
1.getHandler(HttpServletRequest request)方法:該方法是處理當(dāng)前請(qǐng)求找到合適的HandlerMapping,并返回一個(gè)HandlerExecutionChain,HandlerExecutionChain,HandlerExecutionChain包含了具體的處理器(handler)和攔截器列表。
HandlerMapping 默認(rèn)的實(shí)現(xiàn)有org.springframework.web.servlet.handler.BeanNameUrlHandlerMapping
和 org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping
。
@Nullable protected HandlerExecutionChain getHandler(HttpServletRequest request) throws Exception { if (this.handlerMappings != null) { for (HandlerMapping mapping : this.handlerMappings) { HandlerExecutionChain handler = mapping.getHandler(request); if (handler != null) { return handler; } } } return null; }
2.getHandlerAdapter(Object handler) 根據(jù)HandlerExecutionChain中的handler來(lái)獲取處理器適配器(HandlerAdapter),
protected HandlerAdapter getHandlerAdapter(Object handler) throws ServletException { if (this.handlerAdapters != null) { for (HandlerAdapter adapter : this.handlerAdapters) { if (adapter.supports(handler)) { return adapter; } } } throw new ServletException("No adapter for handler [" + handler + "]: The DispatcherServlet configuration needs to include a HandlerAdapter that supports this handler"); }
HandlerAdapter有兩個(gè)默認(rèn)實(shí)現(xiàn)類,分別是 org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter
和 org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter
,前者用于沒(méi)有使用模板引擎的請(qǐng)求,后者用于使用了模板引擎的接口。
實(shí)際處理請(qǐng)求的是HandlerAdapter的handle方法,如果是沒(méi)有使用例如JSP等的模板引擎,handle方法就會(huì)返回null,如果使用了模板引擎就會(huì)返回一個(gè)ModelAndView對(duì)象。
ModelAndView mv = ha.handle(processedRequest, response, mappedHandler.getHandler());
handle方法最終調(diào)用的是Controller接口的 handleRequest(HttpServletRequest request, HttpServletResponse response)
方法來(lái)處理請(qǐng)求。
以SimpleControllerHandlerAdapter#handle方法源碼為例:
@Override @Nullable public ModelAndView handle(HttpServletRequest request, HttpServletResponse response, Object handler) throws Exception { return ((Controller) handler).handleRequest(request, response); }
3.processDispatchResult方法用于處理轉(zhuǎn)發(fā)結(jié)果,該結(jié)果要么是一個(gè)ModelAndView,要么拋異常。
private void processDispatchResult(HttpServletRequest request, HttpServletResponse response, @Nullable HandlerExecutionChain mappedHandler, @Nullable ModelAndView mv, @Nullable Exception exception) throws Exception { boolean errorView = false; if (exception != null) { if (exception instanceof ModelAndViewDefiningException) { logger.debug("ModelAndViewDefiningException encountered", exception); mv = ((ModelAndViewDefiningException) exception).getModelAndView(); } else { Object handler = (mappedHandler != null ? mappedHandler.getHandler() : null); //處理異常 mv = processHandlerException(request, response, handler, exception); errorView = (mv != null); } } // Did the handler return a view to render? if (mv != null && !mv.wasCleared()) { //加載視圖 render(mv, request, response); if (errorView) { WebUtils.clearErrorRequestAttributes(request); } } else { if (logger.isTraceEnabled()) { logger.trace("No view rendering, null ModelAndView returned."); } } if (WebAsyncUtils.getAsyncManager(request).isConcurrentHandlingStarted()) { // Concurrent handling started during a forward return; } if (mappedHandler != null) { // Exception (if any) is already handled.. mappedHandler.triggerAfterCompletion(request, response, null); } }
processDispatchResult
方法中在正常情況下會(huì)調(diào)用render
方法。
4.render方法用來(lái)通過(guò)名稱呈現(xiàn)視圖,它也是請(qǐng)求處理的最后一步。
protected void render(ModelAndView mv, HttpServletRequest request, HttpServletResponse response) throws Exception { // Determine locale for request and apply it to the response. Locale locale = (this.localeResolver != null ? this.localeResolver.resolveLocale(request) : request.getLocale()); response.setLocale(locale); View view; String viewName = mv.getViewName(); if (viewName != null) { // 通過(guò)視圖名稱獲取視圖 view = resolveViewName(viewName, mv.getModelInternal(), locale, request); if (view == null) { throw new ServletException("Could not resolve view with name '" + mv.getViewName() + "' in servlet with name '" + getServletName() + "'"); } } else { // No need to lookup: the ModelAndView object contains the actual View object. view = mv.getView(); if (view == null) { throw new ServletException("ModelAndView [" + mv + "] neither contains a view name nor a " + "View object in servlet with name '" + getServletName() + "'"); } } // Delegate to the View object for rendering. if (logger.isTraceEnabled()) { logger.trace("Rendering view [" + view + "] "); } try { if (mv.getStatus() != null) { response.setStatus(mv.getStatus().value()); } //渲染視圖 view.render(mv.getModelInternal(), request, response); } catch (Exception ex) { if (logger.isDebugEnabled()) { logger.debug("Error rendering view [" + view + "]", ex); } throw ex; } }
DispatcherServlet的render
方法是對(duì)視圖View的封裝,最后調(diào)用的還是View的render方法。
resolveViewName
方法用于解析視圖名稱,它會(huì)通過(guò)視圖解析器ViewResolver的resolveViewName
方法解析視圖并返回一個(gè)視圖View,然后再通過(guò)View的render方法渲染視圖,至于是怎么渲染視圖的這里就不介紹了,感興趣的可以自行查看源碼。
protected View resolveViewName(String viewName, @Nullable Map<String, Object> model, Locale locale, HttpServletRequest request) throws Exception { if (this.viewResolvers != null) { for (ViewResolver viewResolver : this.viewResolvers) { View view = viewResolver.resolveViewName(viewName, locale); if (view != null) { return view; } } } return null; }
到此這篇關(guān)于Java從源碼角度解析SpringMVC執(zhí)行流程的文章就介紹到這了,更多相關(guān)JavaSpringMVC執(zhí)行流程內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家!
相關(guān)文章
SpringMVC實(shí)現(xiàn)RESTful風(fēng)格:@PathVariable注解的使用方式
這篇文章主要介紹了SpringMVC實(shí)現(xiàn)RESTful風(fēng)格:@PathVariable注解的使用方式,具有很好的參考價(jià)值,希望對(duì)大家有所幫助。如有錯(cuò)誤或未考慮完全的地方,望不吝賜教2021-11-11JAVA面試題之Forward與Redirect的區(qū)別詳解
這篇文章主要給大家介紹了在JAVA面試中可能遇到會(huì)遇到的一道題,就是java中Forward與Redirect兩者之前的區(qū)別,文中介紹的非常詳細(xì),對(duì)大家具有一定參考學(xué)習(xí)價(jià)值,需要的朋友們下面來(lái)一起看看吧。2017-05-05Java MAVEN 工程pom配置報(bào)錯(cuò)解決方案
這篇文章主要介紹了Java MAVEN 工程pom配置報(bào)錯(cuò)解決方案,文中通過(guò)示例代碼介紹的非常詳細(xì),對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值,需要的朋友可以參考下2019-10-10