SpringMVC之源碼分析--請求過程

zxhaaa 發布于2019-08-16 11:14 / 1103人閱讀

摘要：概述根據規范，當用戶請求到達應用時，由的方法進行處理，對于而言，處理用戶請求的入口為，通過其父類的攔截處理。最后創建了群方便大家交流，可掃描加入，同時也可加我，共同學習共同進步，謝謝

概述

根據Servlet規范，當用戶請求到達應用時，由Servlet的service()方法進行處理，對于Spring MVC而言，處理用戶請求的入口為DispatcherServlet，通過其父類FrameworkServlet的service()攔截處理。

FrameworkServlet

用戶請求的入口方法為service(request,response)，源碼如下：

/**
 * Override the parent class implementation in order to intercept PATCH requests.
 */
@Override
protected void service(HttpServletRequest request, HttpServletResponse response)
        throws ServletException, IOException {
    HttpMethod httpMethod = HttpMethod.resolve(request.getMethod());
    // Spring3.0增加了PATCH方法攔截處理
    if (httpMethod == HttpMethod.PATCH || httpMethod == null) {
        processRequest(request, response);
    } else { // GET, HEAD, POST, PUT, DELETE, OPTIONS, TRACE
        super.service(request, response);
    }
}

該方法重寫了HttpServlet的service()方法，并增加了PATCH請求的攔截處理，其他諸如GET、POST、PUT等請求則調用父類的service方法，HttpServlet類的service()方法就是根據請求類型進行不同的路由處理，如為GET請求，則路由至doGet()方法處理，以此類推，此處省略源碼。

假如用戶請求為GET，則路由到子類（FrameworkServlet）的doGet()方法進行處理，doGet()源碼如下：

@Override
protected final void doGet(HttpServletRequest request, HttpServletResponse response)
        throws ServletException, IOException {
    processRequest(request, response);
}

其實，所有類型的請求最終都由processRequest()方法進行處理，processRequest方法源碼如下：

protected final void processRequest(HttpServletRequest request, HttpServletResponse response)
        throws ServletException, IOException {

    long startTime = System.currentTimeMillis();
    Throwable failureCause = null;
    // 
    LocaleContext previousLocaleContext = LocaleContextHolder.getLocaleContext();
    // 構建請求(request)的LocalContext上下文，提供基本的作為當前地區的主要語言環境
    LocaleContext localeContext = buildLocaleContext(request);

    RequestAttributes previousAttributes = RequestContextHolder.getRequestAttributes();
    // 構建請求(request)的ServletRequestAttributes對象，保存本次請求的request和response
    ServletRequestAttributes requestAttributes = buildRequestAttributes(request, response, previousAttributes);
    // 異步請求處理的管理核心類
    WebAsyncManager asyncManager = WebAsyncUtils.getAsyncManager(request);
    asyncManager.registerCallableInterceptor(FrameworkServlet.class.getName(), new RequestBindingInterceptor());
    // 綁定request context上線到當前線程
    initContextHolders(request, localeContext, requestAttributes);

    try {
        // 模板方法，調用子類（DispatcherServlet）的doService方法進行處理
        doService(request, response);
    }
    catch (ServletException | IOException ex) {
        failureCause = ex;
        throw ex;
    }
    catch (Throwable ex) {
        failureCause = ex;
        throw new NestedServletException("Request processing failed", ex);
    }

    finally {
        // 接觸請求線程與LocalContext和RequestAttributes的綁定
        resetContextHolders(request, previousLocaleContext, previousAttributes);
        if (requestAttributes != null) {
            requestAttributes.requestCompleted();
        }

        if (logger.isDebugEnabled()) {
            if (failureCause != null) {
                this.logger.debug("Could not complete request", failureCause);
            }
            else {
                if (asyncManager.isConcurrentHandlingStarted()) {
                    logger.debug("Leaving response open for concurrent processing");
                }
                else {
                    this.logger.debug("Successfully completed request");
                }
            }
        }
        // 發布ApplicationEvent事件，可由ApplicationListener進行監聽
        // 繼承ApplicationListener接口，實現onApplicationEvent()接口，并注冊到spring容器，即可捕獲該事件
        publishRequestHandledEvent(request, response, startTime, failureCause);
    }
}

DispatcherServlet

@Override
protected void doService(HttpServletRequest request, HttpServletResponse response) throws Exception {
    if (logger.isDebugEnabled()) {
        String resumed = WebAsyncUtils.getAsyncManager(request).hasConcurrentResult() ? " resumed" : "";
        logger.debug("DispatcherServlet with name "" + getServletName() + """ + resumed +
                " processing " + request.getMethod() + " request for [" + getRequestUri(request) + "]");
    }

    // 如果是include請求，保存request attribute快照數據，并在finally中進行還原
    Map attributesSnapshot = null;
    if (WebUtils.isIncludeRequest(request)) {
        attributesSnapshot = new HashMap<>();
        Enumeration attrNames = request.getAttributeNames();
        while (attrNames.hasMoreElements()) {
            String attrName = (String) attrNames.nextElement();
            if (this.cleanupAfterInclude || attrName.startsWith(DEFAULT_STRATEGIES_PREFIX)) {
                attributesSnapshot.put(attrName, request.getAttribute(attrName));
            }
        }
    }

    // 把環境上下文設置到請求域中
    request.setAttribute(WEB_APPLICATION_CONTEXT_ATTRIBUTE, getWebApplicationContext());
    request.setAttribute(LOCALE_RESOLVER_ATTRIBUTE, this.localeResolver);
    request.setAttribute(THEME_RESOLVER_ATTRIBUTE, this.themeResolver);
    request.setAttribute(THEME_SOURCE_ATTRIBUTE, getThemeSource());

    if (this.flashMapManager != null) {
        FlashMap inputFlashMap = this.flashMapManager.retrieveAndUpdate(request, response);
        if (inputFlashMap != null) {
            request.setAttribute(INPUT_FLASH_MAP_ATTRIBUTE, Collections.unmodifiableMap(inputFlashMap));
        }
        request.setAttribute(OUTPUT_FLASH_MAP_ATTRIBUTE, new FlashMap());
        request.setAttribute(FLASH_MAP_MANAGER_ATTRIBUTE, this.flashMapManager);
    }

    try {
        // 調用請求處理方法
        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);
            }
        }
    }
}

// 請求處理關鍵方法
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);

            // Determine handler for the current request.
            mappedHandler = getHandler(processedRequest);
            if (mappedHandler == null) {
                noHandlerFound(processedRequest, response);
                return;
            }

            // Determine handler adapter for the current request.
            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 (logger.isDebugEnabled()) {
                    logger.debug("Last-Modified value for [" + getRequestUri(request) + "] is: " + lastModified);
                }
                if (new ServletWebRequest(request, response).checkNotModified(lastModified) && isGet) {
                    return;
                }
            }

            if (!mappedHandler.applyPreHandle(processedRequest, response)) {
                return;
            }

            // Actually invoke the 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);
        }
        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);
            }
        }
    }
}

doDispatch()是Spring MVC中重要的方法，用戶處理用戶請求，其主要經過過程如下：

獲取當前請求的Handler

獲取當前請求的Handler Adapter

執行preHandle方法

執行Handle方法，即Controller中的方法

執行postHandle方法

處理返回結果

總結

本文簡要概述了Spring MVC處理用戶請求過程中所涉及的主要方法，對請求處理的流程做了概述，后續將對內部細節進行分析，以加深理解。

最后創建了qq群方便大家交流，可掃描加入，同時也可加我qq：276420284，共同學習、共同進步，謝謝！

GPU云服務器云服務器源碼中文說明之大數據之數據挖掘分析數據分析分析過程過程數據分析

文章版權歸作者所有，未經允許請勿轉載,若此文章存在違規行為，您可以聯系管理員刪除。

轉載請注明本文地址：http://specialneedsforspecialkids.com/yun/71103.html

SpringMVC之源碼分析--HandlerAdapter（二）

摘要：概述本章我們主要分析處理組件的處理流程以及其接口源碼。概括來說，使用組件分為兩步，首先是注冊組件，其次是處理用戶請求，以下針對這兩個過程進行詳細的分析。本系列文章是基于。接下來的幾章將分析提供的適配策略，希望本節對大家能有幫助，謝謝。概述本章我們主要分析Spring處理HandlerAdapter組件的處理流程以及其接口源碼。概括來說，Spring使用HandlerAdapter組...

Eastboat 2019-08-15 17:58 評論0 收藏0
SpringMVC之源碼分析--HandlerMapping（六）

摘要：概述上一節我們分析了的初始化過程，即創建并注冊，本章我們分析下的請求處理過程，即查找。本系列文章是基于。最后創建了群方便大家交流，可掃描加入，同時也可加我，共同學習共同進步，謝謝概述上一節我們分析了RequestMappingHandlerMapping的初始化過程，即創建并注冊HandlerMehtod，本章我們分析下RequestMappingHandlerMapping的請求...

BDEEFE 2019-08-15 17:54 評論0 收藏0
SpringMVC之源碼分析--LocaleResolver和ThemeResolver應用

摘要：需求根據客戶端環境，界面顯示不同的國旗圖案。選擇的技術方案可利用提供的國際化和主題定制來解決。注意此時返回的中沒有國際化及主題相關的信息。修改請求參數的值為荷蘭，即后再發起請求，結果如下與預期一致，測試通過。概述以上分析了Spring MVC的LocaleResolver和ThemeResolver兩個策略解析器，在實際項目中很少使用，尤其是ThemeResolver，花精力去分析...

qpal 2019-08-15 17:43 評論0 收藏0
SpringMVC之源碼分析--HandlerMapping（三）

摘要：與類圖對比，類繼承自抽象類，其又繼承自抽象類，再往上繼承關系與一致。創建初始化上一章我們分析了的創建初始化過程，的創建初始化過程與一樣，方法的入口在抽象類中的方法。至此，代碼編寫完畢。概述本節我們繼續分析HandlerMapping另一個實現類BeanNameUrlHandlerMapping，從類的名字可知，該類會根據請求的url與spring容器中定義的bean的name屬性值...

fsmStudy 2019-08-15 17:49 評論0 收藏0
SpringMVC之源碼分析--HandlerMapping（五）

摘要：概述通過前三章的分析，我們簡要分析了和，但對攔截器部分做詳細的分析，攔截器的加載和初始化是三個相同的部分。概述通過前三章的分析，我們簡要分析了SimpleUrlHandlerMapping、BeanNameUrlHandlerMapping和RequestMappingHandlerMapping，但對攔截器部分做詳細的分析，攔截器的加載和初始化是三個HandlerMapping相...

nanchen2251 2019-08-15 17:54 評論0 收藏0