Spring MVC 處理一般的異常

默認(rèn)處理器異常解析器DefaultHandlerExceptionResolver會(huì)將Spring MVC拋出的異常轉(zhuǎn)換成對(duì)應(yīng)的錯(cuò)誤狀態(tài)碼。該解析器在MVC命名空間配置或MVC Java配置的方式下默認(rèn)已經(jīng)被注冊(cè)了，另外，通過DispatcherServlet注冊(cè)也是可行的（即不使用MVC命名空間或Java編程方式進(jìn)行配置的時(shí)候）。下表列出了該解析器能處理的一些異常，及他們對(duì)應(yīng)的狀態(tài)碼。

以下待翻譯。

The DefaultHandlerExceptionResolver works transparently by setting the status of the response. However, it stops short of writing any error content to the body of the response while your application may need to add developer- friendly content to every error response for example when providing a REST API. You can prepare a ModelAndView and render error content through view resolution?--?i.e. by configuring a ContentNegotiatingViewResolver, MappingJackson2JsonView, and so on. However, you may prefer to use@ExceptionHandler methods instead.

If you prefer to write error content via @ExceptionHandler methods you can extend ResponseEntityExceptionHandler instead. This is a convenient base for @ControllerAdvice classes providing an @ExceptionHandler method to handle standard Spring MVC exceptions and return ResponseEntity. That allows you to customize the response and write error content with message converters. See the ResponseEntityExceptionHandler javadocs for more details.