简介
咱们都知道，springmvc是客户端和服务端的桥梁，那么它是怎么运行的呢？
类图
大家都知道，springmvc的核心处理类是DispatcherServlet，它是如果被执行的？
从下图可以看出，DispatcherServlet继承了FrameworkServlet
而FrameworkServlet继承了HttpServletBean，实现了ApplicationContextAware
HttpServletBean继承了HttpServlet
HttpServlet继承了GenericServlet
GenericServlet实现了Servlet接口
继承关系及执行流程
从源码看执行流程
从关系图可以看出，springmvc是基于Servlet实现的，咱们知道，当一个请求到达时首先请求Servlet的service方法
Servlet.service()
咱们知道Servlet是一个接口，那么想找它的service实现方法必须去它的实现类找
咱们先找GenericServlet
public abstract void service(ServletRequest req, ServletResponse res)
throws ServletException, IOException;
发现GenericServlet.service是一个抽象方法，那么肯定是它的子类进行实现了
继续找GenericServlet的子类HttpServlet
HttpServlet.service(ServletRequest req, ServletResponse res)
点进来之后大家会发现，HttpServlet实现了service方法
public void service(ServletRequest req, ServletResponse res)
throws ServletException, IOException{
HttpServletRequest request;
HttpServletResponse response;
//验证
if (!(req instanceof HttpServletRequest &&
res instanceof HttpServletResponse)) {
throw new ServletException("non-HTTP request or response");
}
//强转
request = (HttpServletRequest) req;
response = (HttpServletResponse) res;
//调用当前类的service方法
service(request, response);
}
那么咱们继续看当前类的service(HttpServletRequest req, HttpServletResponse resp)方法
//开个玩笑，可能大家有些疑问，这个方法没有做其他处理啊，是的，如果这个方法处理了，咱们就不会认为DispatcherServlet是个核心方法了。
//这个方法主要的作用就是根据请求方式转发请求
//doGet、doHead、doPost、doPut、doDelete、doOptions、doTrace，咱们点进去这些方法发现方法的修改符为protected，那么咱们找下它的子类有没有重写
protected void service(HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException
{
String method = req.getMethod();
if (method.equals(METHOD_GET)) {
long lastModified = getLastModified(req);
if (lastModified == -1) {
doGet(req, resp);
} else {
long ifModifiedSince = req.getDateHeader(HEADER_IFMODSINCE);
if (ifModifiedSince < lastModified) {
maybeSetLastModified(resp, lastModified);
doGet(req, resp);
} else {
resp.setStatus(HttpServletResponse.SC_NOT_MODIFIED);
}
}
} else if (method.equals(METHOD_HEAD)) {
long lastModified = getLastModified(req);
maybeSetLastModified(resp, lastModified);
doHead(req, resp);
} else if (method.equals(METHOD_POST)) {
doPost(req, resp);
} else if (method.equals(METHOD_PUT)) {
doPut(req, resp);
} else if (method.equals(METHOD_DELETE)) {
doDelete(req, resp);
} else if (method.equals(METHOD_OPTIONS)) {
doOptions(req,resp);
} else if (method.equals(METHOD_TRACE)) {
doTrace(req,resp);
} else {
String errMsg = lStrings.getString("http.method_not_implemented");
Object[] errArgs = new Object[1];
errArgs[0] = method;
errMsg = MessageFormat.format(errMsg, errArgs);
resp.sendError(HttpServletResponse.SC_NOT_IMPLEMENTED, errMsg);
}
}
FrameworkServlet.doGet、doHead、doPost、doPut、doDelete、doOptions、doTrace
咱们点进去之后发现所有的方法都调用了同一个方法processRequest(request, response);，那么咱们继续看下这个方法做了哪些事情
//大家点进来后发现这个方法除了初始化一些数据外，就调用了一个doService(request, response)方法
//没错，这个就是一个核心的方法
protected final void processRequest(HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {
long startTime = System.currentTimeMillis();
Throwable failureCause = null;
LocaleContext previousLocaleContext = LocaleContextHolder.getLocaleContext();
LocaleContext localeContext = buildLocaleContext(request);
RequestAttributes previousAttributes = RequestContextHolder.getRequestAttributes();
ServletRequestAttributes requestAttributes = buildRequestAttributes(request, response, previousAttributes);
WebAsyncManager asyncManager = WebAsyncUtils.getAsyncManager(request);
asyncManager.registerCallableInterceptor(FrameworkServlet.class.getName(), new RequestBindingInterceptor());
initContextHolders(request, localeContext, requestAttributes);
try {
//大家读源码的时候一定要关注下do...方法，一般它是要进行干活了
doService(request, response);
}catch (ServletException | IOException ex) {
failureCause = ex;
throw ex;
}catch (Throwable ex) {
failureCause = ex;
throw new NestedServletException("Request processing failed", ex);
}
finally {
resetContextHolders(request, previousLocaleContext, previousAttributes);
if (requestAttributes != null) {
requestAttributes.requestCompleted();
}
logResult(request, response, failureCause, asyncManager);
publishRequestHandledEvent(request, response, startTime, failureCause);
}
}
FrameworkServlet.doService
//大家发现FrameworkServlet.doService方法是一个抽象类，咱们接着找它的子类看看谁进行实现
protected abstract void doService(HttpServletRequest request, HttpServletResponse response)
throws Exception;
DispatcherServlet.doService(HttpServletRequest request, HttpServletResponse response)
大家点进来发现，这个方法除了给属性赋值外就调用了doDispatch(request, response)方法，没错，真正干活的方法终于找到了
protected void doService(HttpServletRequest request, HttpServletResponse response) throws Exception {
logRequest(request);
Map<String, Object> 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));
}
}
}
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);
}
}
}
}
DispatcherServlet.doDispatch(request, response)
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);
// 得到 HandlerMapping
mappedHandler = getHandler(processedRequest);
if (mappedHandler == null) {
noHandlerFound(processedRequest, response);
return;
}
// 得到 HandlerAdapter
HandlerAdapter ha = getHandlerAdapter(mappedHandler.getHandler());
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;
}
// 执行咱们写的controller方法，返回 ModelAndView
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) {
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()) {
if (mappedHandler != null) {
mappedHandler.applyAfterConcurrentHandlingStarted(processedRequest, response);
}
}
else {
if (multipartRequestParsed) {
cleanupMultipart(processedRequest);
}
}
}
}
总结
Springmvc整体流程相对还是比较简单，路已经铺好，具体钻研多深看大家了~~~
PS：如果您觉得文章还不错，浪费您半分钟的时间帮忙点点关注~~~
909
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
