Spring MVC : 工具 DefaultHandlerExceptionResolver

最新推荐文章于 2024-08-19 12:00:00 发布
最新推荐文章于 2024-08-19 12:00:00 发布
阅读量7.9k 收藏 16
点赞数 2
分类专栏： Spring MVC 分析
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/andy_zhang2007/article/details/89294739
版权

DefaultHandlerExceptionResolver是Spring MVC对接口HandlerExceptionResolver的一个内置实现，这个HandlerExceptionResolver，顾名思义，是作为"缺省"HandlerExceptionResolver被使用的，也就是说，如果其他HandlerExceptionResolver不能处理指定的异常，最后会使用DefaultHandlerExceptionResolver来处理。而DefaultHandlerExceptionResolver能够解析标准Spring MVC异常，将其翻译成相应的HTTP状态码，通过response.sendError方法处理响应。以下是DefaultHandlerExceptionResolver处理的异常和相应的HTTP状态字的对照表 :

Spring MVC 标准异常HTTP状态码介绍
HttpRequestMethodNotSupportedException405 (SC_METHOD_NOT_ALLOWED)HTTP方法不支持
HttpMediaTypeNotSupportedException415 (SC_UNSUPPORTED_MEDIA_TYPE)MIME类型不支持
HttpMediaTypeNotAcceptableException406 (SC_NOT_ACCEPTABLE)MIME类型不被接受
MissingPathVariableException500 (SC_INTERNAL_SERVER_ERROR)路径参数缺失
MissingServletRequestParameterException400 (SC_BAD_REQUEST)Servlet请求参数缺失
ServletRequestBindingException400 (SC_BAD_REQUEST)Servlet请求处理过程中的绑定异常
ConversionNotSupportedException500 (SC_INTERNAL_SERVER_ERROR)不支持该类型转换
TypeMismatchException400 (SC_BAD_REQUEST)类型不匹配
HttpMessageNotReadableException400 (SC_BAD_REQUEST)HTTP消息不可读
使用者:HttpMessageConverter#read
HttpMessageNotWritableException500 (SC_INTERNAL_SERVER_ERROR)HTTP消息不可写
使用者:HttpMessageConverter#write
MethodArgumentNotValidException400 (SC_BAD_REQUEST)方法参数值验证失败
MissingServletRequestPartException400 (SC_BAD_REQUEST)multipart/form-data请求时,
part名称指定的part数据不存在
BindException400 (SC_BAD_REQUEST)Spring验证框架中的绑定异常
NoHandlerFoundException404 (SC_NOT_FOUND)没有找到能处理该请求的handler
AsyncRequestTimeoutException503 (SC_SERVICE_UNAVAILABLE)异步请求超时

上表中提到的异常之间的关系如下 :
在这里插入图片描述

异常解析器DefaultHandlerExceptionResolver是Spring MVC的前端控制器DispatcherServlet缺省启用的HandlerExceptionResolver之一，并且被设置为最低优先级。

DefaultHandlerExceptionResolver是Spring MVC配置机制WebMvcConfigurationSupport缺省定义的一个HandlerExceptionResolver。

DefaultHandlerExceptionResolver的核心方法是#doResolveException,该方法内部根据异常的类型调用不同的方法将异常翻译成相应的HTTP状态码并sendError到响应对象，并且返回值是一个空ModelAdnView对象，也就是一个其#isEmpty方法总是为true的对象，此返回值告诉调用者：请使用缺省视图渲染相应的错误信息。

源代码解析

package org.springframework.web.servlet.mvc.support;


public class DefaultHandlerExceptionResolver extends AbstractHandlerExceptionResolver {

	/**
	 * Log category to use when no mapped handler is found for a request.
	 * @see #pageNotFoundLogger
	 */
	public static final String PAGE_NOT_FOUND_LOG_CATEGORY = 
		"org.springframework.web.servlet.PageNotFound";

	/**
	 * Additional logger to use when no mapped handler is found for a request.
	 * @see #PAGE_NOT_FOUND_LOG_CATEGORY
	 */
	protected static final Log pageNotFoundLogger = LogFactory.getLog(PAGE_NOT_FOUND_LOG_CATEGORY);


	/**
	 * Sets the #setOrder(int) order to  #LOWEST_PRECEDENCE.
	 */
	public DefaultHandlerExceptionResolver() {
		// 注意该构造函数中将该异常解析器的优先级设置为最低
		setOrder(Ordered.LOWEST_PRECEDENCE);
		setWarnLogCategory(getClass().getName());
	}


	// 根据参数 ex 异常对象的类型解析参数，将其转换成一个 ModelAndView 对象返回，
	// 并且注意该过程中涉及到对 response 头部的设置，已经对其调用  sendError() .
	// 如果参数 ex 不能被当前异常处理器处理，返回 null
	// 该方法对基类定义的该方法提供了实现，该方法会被基类公开方法 resolveException() 使用，
	// resolveException() 是接口 HandlerExceptionResolver 所定义的方法
	@Override
	@Nullable
	protected ModelAndView doResolveException(
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler, 
			Exception ex) {

		try {
			if (ex instanceof HttpRequestMethodNotSupportedException) {
				return handleHttpRequestMethodNotSupported(
						(HttpRequestMethodNotSupportedException) ex, request, response, handler);
			}
			else if (ex instanceof HttpMediaTypeNotSupportedException) {
				return handleHttpMediaTypeNotSupported(
						(HttpMediaTypeNotSupportedException) ex, request, response, handler);
			}
			else if (ex instanceof HttpMediaTypeNotAcceptableException) {
				return handleHttpMediaTypeNotAcceptable(
						(HttpMediaTypeNotAcceptableException) ex, request, response, handler);
			}
			else if (ex instanceof MissingPathVariableException) {
				return handleMissingPathVariable(
						(MissingPathVariableException) ex, request, response, handler);
			}
			else if (ex instanceof MissingServletRequestParameterException) {
				return handleMissingServletRequestParameter(
						(MissingServletRequestParameterException) ex, request, response, handler);
			}
			else if (ex instanceof ServletRequestBindingException) {
				return handleServletRequestBindingException(
						(ServletRequestBindingException) ex, request, response, handler);
			}
			else if (ex instanceof ConversionNotSupportedException) {
				return handleConversionNotSupported(
						(ConversionNotSupportedException) ex, request, response, handler);
			}
			else if (ex instanceof TypeMismatchException) {
				return handleTypeMismatch(
						(TypeMismatchException) ex, request, response, handler);
			}
			else if (ex instanceof HttpMessageNotReadableException) {
				return handleHttpMessageNotReadable(
						(HttpMessageNotReadableException) ex, request, response, handler);
			}
			else if (ex instanceof HttpMessageNotWritableException) {
				return handleHttpMessageNotWritable(
						(HttpMessageNotWritableException) ex, request, response, handler);
			}
			else if (ex instanceof MethodArgumentNotValidException) {
				return handleMethodArgumentNotValidException(
						(MethodArgumentNotValidException) ex, request, response, handler);
			}
			else if (ex instanceof MissingServletRequestPartException) {
				return handleMissingServletRequestPartException(
						(MissingServletRequestPartException) ex, request, response, handler);
			}
			else if (ex instanceof BindException) {
				return handleBindException((BindException) ex, request, response, handler);
			}
			else if (ex instanceof NoHandlerFoundException) {
				return handleNoHandlerFoundException(
						(NoHandlerFoundException) ex, request, response, handler);
			}
			else if (ex instanceof AsyncRequestTimeoutException) {
				return handleAsyncRequestTimeoutException(
						(AsyncRequestTimeoutException) ex, request, response, handler);
			}
		}
		catch (Exception handlerEx) {
			if (logger.isWarnEnabled()) {
				logger.warn("Failure while trying to resolve exception [" 
				+ ex.getClass().getName() + "]", handlerEx);
			}
		}
		return null;
	}

	/**
	 * Handle the case where no request handler method was found for the particular HTTP request 
	 * method.
	 * The default implementation logs a warning, sends an HTTP 405 error, sets the "Allow" header,
	 * and returns an empty ModelAndView. Alternatively, a fallback view could be chosen,
	 * or the HttpRequestMethodNotSupportedException could be rethrown as-is.
	 * @param ex the HttpRequestMethodNotSupportedException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler, or null if none chosen
	 * at the time of the exception (for example, if multipart resolution failed)
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleHttpRequestMethodNotSupported(
			HttpRequestMethodNotSupportedException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		String[] supportedMethods = ex.getSupportedMethods();
		if (supportedMethods != null) {
			response.setHeader("Allow", StringUtils.arrayToDelimitedString(supportedMethods, ", "));
		}
		response.sendError(HttpServletResponse.SC_METHOD_NOT_ALLOWED, ex.getMessage());
		return new ModelAndView();
	}

	/**
	 * Handle the case where no org.springframework.http.converter.HttpMessageConverter message 
	 * converters were found for the PUT or POSTed content.
	 * The default implementation sends an HTTP 415 error, sets the "Accept" header,
	 * and returns an empty ModelAndView. Alternatively, a fallback view could
	 * be chosen, or the HttpMediaTypeNotSupportedException could be rethrown as-is.
	 * @param ex the HttpMediaTypeNotSupportedException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleHttpMediaTypeNotSupported(HttpMediaTypeNotSupportedException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_UNSUPPORTED_MEDIA_TYPE);
		List<MediaType> mediaTypes = ex.getSupportedMediaTypes();
		if (!CollectionUtils.isEmpty(mediaTypes)) {
			response.setHeader("Accept", MediaType.toString(mediaTypes));
		}
		return new ModelAndView();
	}

	/**
	 * Handle the case where no org.springframework.http.converter.HttpMessageConverter message 
	 * converters
	 * were found that were acceptable for the client (expressed via the Accept header.
	 * The default implementation sends an HTTP 406 error and returns an empty ModelAndView.
	 * Alternatively, a fallback view could be chosen, or the HttpMediaTypeNotAcceptableException
	 * could be rethrown as-is.
	 * @param ex the HttpMediaTypeNotAcceptableException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleHttpMediaTypeNotAcceptable(HttpMediaTypeNotAcceptableException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_NOT_ACCEPTABLE);
		return new ModelAndView();
	}

	/**
	 * Handle the case when a declared path variable does not match any extracted URI variable.
	 * The default implementation sends an HTTP 500 error, and returns an empty ModelAndView.
	 * Alternatively, a fallback view could be chosen, or the MissingPathVariableException
	 * could be rethrown as-is.
	 * @param ex the MissingPathVariableException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 * @since 4.2
	 */
	protected ModelAndView handleMissingPathVariable(MissingPathVariableException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_INTERNAL_SERVER_ERROR, ex.getMessage());
		return new ModelAndView();
	}

	/**
	 * Handle the case when a required parameter is missing.
	 * The default implementation sends an HTTP 400 error, and returns an empty ModelAndView.
	 * Alternatively, a fallback view could be chosen, or the MissingServletRequestParameterException
	 * could be rethrown as-is.
	 * @param ex the MissingServletRequestParameterException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleMissingServletRequestParameter(
			MissingServletRequestParameterException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_BAD_REQUEST, ex.getMessage());
		return new ModelAndView();
	}

	/**
	 * Handle the case when an unrecoverable binding exception occurs - e.g. required header, 
	 * required cookie.
	 * The default implementation sends an HTTP 400 error, and returns an empty ModelAndView.
	 * Alternatively, a fallback view could be chosen, or the exception could be rethrown as-is.
	 * @param ex the exception to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleServletRequestBindingException(ServletRequestBindingException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_BAD_REQUEST, ex.getMessage());
		return new ModelAndView();
	}

	/**
	 * Handle the case when a org.springframework.web.bind.WebDataBinder conversion cannot occur.
	 * The default implementation sends an HTTP 500 error, and returns an empty ModelAndView.
	 * Alternatively, a fallback view could be chosen, or the ConversionNotSupportedException could be
	 * rethrown as-is.
	 * @param ex the ConversionNotSupportedException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleConversionNotSupported(ConversionNotSupportedException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		sendServerError(ex, request, response);
		return new ModelAndView();
	}

	/**
	 * Handle the case when a org.springframework.web.bind.WebDataBinder conversion error occurs.
	 * The default implementation sends an HTTP 400 error, and returns an empty ModelAndView.
	 * Alternatively, a fallback view could be chosen, or the TypeMismatchException could be 
	 * rethrown as-is.
	 * @param ex the TypeMismatchException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleTypeMismatch(TypeMismatchException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_BAD_REQUEST);
		return new ModelAndView();
	}

	/**
	 * Handle the case where a org.springframework.http.converter.HttpMessageConverter message 
	 * converter cannot read from a HTTP request.
	 * The default implementation sends an HTTP 400 error, and returns an empty ModelAndView.
	 * Alternatively, a fallback view could be chosen, or the HttpMessageNotReadableException could be
	 * rethrown as-is.
	 * @param ex the HttpMessageNotReadableException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleHttpMessageNotReadable(HttpMessageNotReadableException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_BAD_REQUEST);
		return new ModelAndView();
	}

	/**
	 * Handle the case where a
	 * org.springframework.http.converter.HttpMessageConverter message converter
	 * cannot write to a HTTP request.
	 * The default implementation sends an HTTP 500 error, and returns an empty ModelAndView.
	 * Alternatively, a fallback view could be chosen, or the HttpMessageNotWritableException could
	 * be rethrown as-is.
	 * @param ex the HttpMessageNotWritableException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleHttpMessageNotWritable(HttpMessageNotWritableException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		sendServerError(ex, request, response);
		return new ModelAndView();
	}

	/**
	 * Handle the case where an argument annotated with @Valid such as
	 * an RequestBody or RequestPart argument fails validation.
	 * By default, an HTTP 400 error is sent back to the client.
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleMethodArgumentNotValidException(MethodArgumentNotValidException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_BAD_REQUEST);
		return new ModelAndView();
	}

	/**
	 * Handle the case where an RequestPart @RequestPart, a MultipartFile,
	 * or a javax.servlet.http.Part argument is required but is missing.
	 * By default, an HTTP 400 error is sent back to the client.
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleMissingServletRequestPartException(
			MissingServletRequestPartException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		response.sendError(HttpServletResponse.SC_BAD_REQUEST, ex.getMessage());
		return new ModelAndView();
	}

	/**
	 * Handle the case where an ModelAttribute @ModelAttribute method
	 * argument has binding or validation errors and is not followed by another
	 * method argument of type BindingResult.
	 * By default, an HTTP 400 error is sent back to the client.
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 */
	protected ModelAndView handleBindException(BindException ex, HttpServletRequest request,
			HttpServletResponse response, @Nullable Object handler) throws IOException {

		response.sendError(HttpServletResponse.SC_BAD_REQUEST);
		return new ModelAndView();
	}

	/**
	 * Handle the case where no handler was found during the dispatch.
	 * The default implementation sends an HTTP 404 error and returns an empty
	 * ModelAndView. Alternatively, a fallback view could be chosen,
	 * or the NoHandlerFoundException could be rethrown as-is.
	 * @param ex the NoHandlerFoundException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler, or null if none chosen
	 * at the time of the exception (for example, if multipart resolution failed)
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 * @since 4.0
	 */
	protected ModelAndView handleNoHandlerFoundException(NoHandlerFoundException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		pageNotFoundLogger.warn(ex.getMessage());
		response.sendError(HttpServletResponse.SC_NOT_FOUND);
		return new ModelAndView();
	}

	/**
	 * Handle the case where an async request timed out.
	 * The default implementation sends an HTTP 503 error.
	 * @param ex the AsyncRequestTimeoutException to be handled
	 * @param request current HTTP request
	 * @param response current HTTP response
	 * @param handler the executed handler, or null if none chosen
	 * at the time of the exception (for example, if multipart resolution failed)
	 * @return an empty ModelAndView indicating the exception was handled
	 * @throws IOException potentially thrown from HttpServletResponse#sendError
	 * @since 4.2.8
	 */
	protected ModelAndView handleAsyncRequestTimeoutException(AsyncRequestTimeoutException ex,
			HttpServletRequest request, HttpServletResponse response, @Nullable Object handler) 
			throws IOException {

		if (!response.isCommitted()) {
			response.sendError(HttpServletResponse.SC_SERVICE_UNAVAILABLE);
		}
		else {
			logger.warn("Async request timed out");
		}
		return new ModelAndView();
	}

	/**
	 * Invoked to send a server error. Sets the status to 500 and also sets the
	 * request attribute "javax.servlet.error.exception" to the Exception.
	 */
	protected void sendServerError(Exception ex, HttpServletRequest request, 
			HttpServletResponse response) throws IOException {

		request.setAttribute("javax.servlet.error.exception", ex);
		response.sendError(HttpServletResponse.SC_INTERNAL_SERVER_ERROR);
	}

}

参考文章

安迪源文
关注
专栏目录
springmvc基础知识（18）：HandlerExceptionResolver异常处理
YellowStar的博客
05-25 9950
在开发中，异常很常见的，我们需要捕捉异常并处理它，才能保证程序不被终止。最常见的异常处理方法就是用try catch来捕捉异常。 Spring MVC通过HandlerExceptionResolver处理程序的异常，包括 Handler 映射、数据绑定以及目标方法执行时发生的异常。 SpringMVC 提供的 HandlerExceptionResolver 的实...
SpringMVC(8)——注解配置SpringMVC、SpringMVC汇总、＜mvc:annotation-driven＞作用
zjr_java的博客
03-28 505
同时它还提供了：数据绑定支持，@NumberFormatannotation支持，@DateTimeFormat支持，@Valid支持，读写XML的支持（JAXB，读写JSON的支持（Jackson）。我们处理响应ajax请求时，就使用到了对json的支持（配置之后，在加入了jackson的core和mapper包之后，不写配置文件也能自动转换成json，之前在别的章节就演示过了）通过源码分析DispatcherServlet调用各个组件处理请求的过程。说明：不演示文件上传是否实现。
`DefaultHandlerExceptionResolver` 是 Spring MVC 提供的一个异常处理器，用于解析控制器方法抛出的异常
BLOG域名:programb.blog.csdn.net
07-25 742
在该方法中，我们将自定义的异常处理器添加到异常解析器列表中，以确保优先级高于默认的异常处理器。同时，我们还添加了一个。是 Spring MVC 提供的一个异常处理器，用于解析控制器方法抛出的异常。要使用自定义的异常处理器，需要在 Spring MVC 的配置文件中将其注册为。，以便能够使用默认的异常处理器处理未被自定义处理器捕获的异常。在该方法中，我们将异常信息设置为请求属性。方法，该方法用于处理控制器方法抛出的异常。在上面的示例中，我们创建了一个实现了。在上面的示例中，我们创建了一个实现了。
解决org.springframework.web.method.annotation.MethodArgumentTypeMismatchException（SpringBoot框架配置类型转换器）
最新发布
2301_76632762的博客
08-19 842
在JAVA开发中遇到org.springframework.web.method.annotation.MethodArgumentTypeMismatchException异常问题，记录从分析，排查到解决问题的过程。
SpringMVC---异常处理DefaultHandlerExceptionResolver
qq_39093474的博客
01-09 909
一：DefaultHandlerExceptionResolver 对一些特殊的异常进行处理，比 如NoSuchRequestHandlingMethodException、HttpReques tMethodNotSupportedException、HttpMediaTypeNotSuppo rtedException、HttpMediaTypeNotAcceptableException ...
org.springframework.web.servlet.mvc.support.DefaultHandlerExceptionResolver 怎么解决
马一文
11-11 2万+
@RequestMapping(value = "/json", method = RequestMethod.GET) public String listSystemConfigJson(@RequestBody SystemConfig systemConfig ) {} 看我的代码，     我们知道，get传参是路径传参的。RequestBody 是接受内容里面的参数。这个是g...
Spring MVC 异常处理 - DefaultHandlerExceptionResolver
weixin_30378311的博客
07-02 343
对一些特殊的异常进行处理，比如方法类型不匹配, 转换错误. 转载于:https://www.cnblogs.com/eason-d/p/9256128.html
Spring源码——Spring MVC
等一杯咖啡的博客
11-22 1616
前言 内容主要参考自《Spring源码深度解析》一书，算是读书笔记或是原书的补充。进入正文后可能会引来各种不适，毕竟阅读源码是件极其痛苦的事情。 本文主要涉及书中第十一章的部分，依照书中内容以及个人理解对Spring源码进行了注释，详见Github仓库：https://github.com/MrSorrow/spring-framework Spring框架提供了构建Web应用程序的全功能MVC模...
第二课：通过MVC原理，自定义MVC框架实现1
08-08
Spring MVC还提供了默认的异常处理器，如ResponseStatusExceptionResolver和DefaultHandlerExceptionResolver，以及SimpleMappingExceptionResolver，后者可以将不同类型的异常映射到不同的错误页面。 2. ...
Spring-MVC学习 (maven工程) (尚硅谷版)
qq_61125494的博客
10-24 773
此文章，借助了尚硅谷的。专攻mvc的配置
Spring MVC 接收请求参数所有方式总结，看完记得收藏~
weixin_46898270的博客
06-15 622
SpringMVC请求参数接收 其实一般的表单或者JSON数据的请求都是相对简单的，一些复杂的处理主要包括URL路径参数、文件上传、数组或者列表类型数据等。 另外，关于参数类型中存在日期类型属性(例如java.util.Date、java.sql.Date、java.time.LocalDate、java.time.LocalDateTime)，解析的时候一般需要自定义实现的逻辑实现String->日期类型的转换。 其实道理很简单，日期相关的类型对于每个国家、每个时区甚至每个使用者来说认知都不一定相同
Spring MVC 源码- HandlerExceptionResolver 组件
Coder_Boy_的博客
02-25 770
实现 HandlerExceptionResolver、Ordered 接口，HandlerExceptionResolver 抽象类，作为所有 HandlerExceptionResolver 实现类的。，继承 AbstractHandlerExceptionResolver 抽象类，默认 HandlerExceptionResolver 实现类，针对各种异常，设置错误响应码。的实现类没有特别多，不过也采用了组合模式，如果某个异常处理器进行处理了，也就是返回的 ModeAndView 不为。
精尽Spring MVC源码分析 - HandlerExceptionResolver 组件
gman344的博客
06-10 631
该系列文档是本人在学习 Spring MVC 的源码过程中总结下来的，可能对读者不太友好，请结合我的源码注释 Spring MVC 源码分析 GitHub 地址 进行阅读 Spring 版本：5.1.14.RELEASE 该系列其他文档请查看：《精尽 Spring MVC 源码分析 - 文章导读》 HandlerExceptionResolver 组件 HandlerExceptionResolver 组件，处理器异常解析器，将处理器（ handler ）执行时发生的异常（也就是处理请求，执行方法的过..
springMVC绑定参数时报错DefaultHandlerExceptionResolver解决办法
xiaozaq的博客
10-17 7279
public class User { int id; String username; String password; String realName; String email; String phone; Set roles; } UserAction.java @RequestMapping(value = "list") @ResponseBody publ
springmvc之异常处理DefaultHandlerExceptionResolver
hijk7的博客
07-11 394
springmvc之异常处理DefaultHandlerExceptionResolver
spring mvc框架的异常处理机制
z804547022的博客
11-26 160
Spring MVC处理异常主要依赖于HandlerExceptionResolver接口及其实现类默认会启动它的三个对象：   org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver org.springframework.web.servlet.mvc.anno...
13.3、异常处理——DefaultHandlerExceptionResolver
u010502101的博客
11-17 1万+
当程序发生异常时，DefaultHandlerExceptionResolver异常解析器默认可以解析指定的异常，见下面的源码，默认可以解析HttpRequestMethodNotSupportedException、HttpMediaTypeNotSupportedException等异常类，当有这些类的异常发生时，默认交给DefaultHandlerExceptionResolver异常解析器进
异常处理-DefaultHandlerExceptionResolver
热门推荐
super的博客
05-07 2万+
工作中遇到springmvc框架定义的方法中使用了【@RequestBody】 这个注解代码如下： @RequestMapping(value = "create", method = RequestMethod.POST) @ResponseBody public ResultData createOrder(@RequestBody PrintOrders printOrders, Htt...
经验积累-使用记录-DefaultHandlerExceptionResolver
lzhlove的博客
04-15 1740
修改DefaultHandlerExceptionResolver优先级 拦截400异常,拦截405异常. hibernate-validate校验异常处理. 如何让自定义异常处理器,优先于DefaultHandlerExceptionResolver执行.
精通Spring MVC：快速入门指南
"Spring MVC 入门教程，适合想要学习基于Java的Web应用程序开发的读者。书中涵盖了Spring Framework的基础，Servlet和JavaServer Pages (JSP)的速成课程，为理解Spring MVC打下基础。" Spring MVC是Spring框架的一...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值