HandlerInterceptor和HandlerExceptionResolver 如何在DispatcherServlet中生效？

HandlerInterceptor拦截Controller，实现pre和post方法。

HandlerExceptionResolver全局try-catch  处理Controller里的异常。

这两个类如何在DispatcherServlet中生效？

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 || mappedHandler.getHandler() == null) {
					noHandlerFound(processedRequest, response);
					return;
				}

				// Determine handler adapter for the current request.
				//判断这个请求到底用哪个controller的哪个方法来处理。
				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;
					}
				}
				// 在执行请求controller之前的操作，跟进可以看到里面是拿到所有注册的 HandlerInterceptor， 执行HandlerInterceptor.preHandle（HttpServletRequest request, HttpServletResponse response, Object handler）方法。
				if (!mappedHandler.applyPreHandle(processedRequest, response)) {
					return;
				}

				// Actually invoke the handler.
				//真正的去调用controller方法的地方，这里的ha是 AbstractHandlerMethodAdapter ，可以跟进看看其子类RequestMappingHandlerAdapter的 handleInternal（）方法。真正执行controller方法的是 mav = invokeHandlerMethod(request, response, handlerMethod);这一步
				mv = ha.handle(processedRequest, response, mappedHandler.getHandler());

				if (asyncManager.isConcurrentHandlingStarted()) {
					return;
				}

				applyDefaultViewName(processedRequest, mv);
				//在执行请求controller之后的操作，跟进可以看到里面是拿到所有注册的 HandlerInterceptor， 执行HandlerInterceptor.postHandle（request, response, this.handler, 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);
			}
			//上面的两个catch都可以看到用dispatchException 接收了异常，然后这一步是进行异常处理，可以看到的是用HandlerExceptionResolver 进行遍历处理异常，只要处理到handlerExceptionResolver.resolveException(request, response, handler, ex)不为空的返回即break.
			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);
				}
			}
		}
	}