blocks|key|2923370|text|我认为ResponseEntityExceptionHandler符合您的要求。HTTP+400的一段示例代码：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2923371|@ControllerAdvice
public+class+MyExceptionHandler+extends+ResponseEntityExceptionHandler+{

++@ResponseStatus(value+=+HttpStatus.BAD_REQUEST)
++@ExceptionHandler({HttpMessageNotReadableException.class,+MethodArgumentNotValidException.class,
++++++HttpRequestMethodNotSupportedException.class})
++public+ResponseEntity<Object>+badRequest(HttpServletRequest+req,+Exception+exception)+{
++++//+...
++}
}|code-block|syntax|javascript|2923372|您可以查看此post|2923373|entityMap|0|LINK|mutability|MUTABLE|url|http://springinpractice.com/2013/10/09/generating-json-error-object-responses-with-spring-web-mvc^0|3|U|0|0|6|4|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

I think <code>ResponseEntityExceptionHandler</code> meets your requirements. A sample piece of code for HTTP 400:

<pre><code>@ControllerAdvice
public class MyExceptionHandler extends ResponseEntityExceptionHandler {

 @ResponseStatus(value = HttpStatus.BAD_REQUEST)
 @ExceptionHandler({HttpMessageNotReadableException.class, MethodArgumentNotValidException.class,
 HttpRequestMethodNotSupportedException.class})
 public ResponseEntity&lt;Object&gt; badRequest(HttpServletRequest req, Exception exception) {
 // ...
 }
}
</code></pre>

You can check this <a href="http://springinpractice.com/2013/10/09/generating-json-error-object-responses-with-spring-web-mvc">post</a>

blocks|key|2710726|text|默认情况下，Spring+Boot会向json提供错误详细信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2710727|curl+-v+localhost:8080/greet+%7C+json_pp
[...]
<+HTTP/1.1+400+Bad+Request
[...]
{
+++"timestamp"+:+1413313361387,
+++"exception"+:+"org.springframework.web.bind.MissingServletRequestParameterException",
+++"status"+:+400,
+++"error"+:+"Bad+Request",
+++"path"+:+"/greet",
+++"message"+:+"Required+String+parameter+'name'+is+not+present"
}|code-block|syntax|javascript|2710728|它也适用于所有类型的请求映射错误。查看这篇文章http://www.jayway.com/2014/10/19/spring-boot-error-responses/|offset|length|2710729|如果您想要创建，请将其记录到NoSQL。您可以创建@ControllerAdvice并将其记录在其中，然后重新抛出异常。documentation+https://spring.io/blog/2013/11/01/exception-handling-in-spring-mvc中有一个示例|2710730|entityMap|0|LINK|mutability|MUTABLE|url|http://www.jayway.com/2014/10/19/spring-boot-error-responses/|1|https://spring.io/blog/2013/11/01/exception-handling-in-spring-mvc^0|0|0|N|1P|0|0|22|1U|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@$I|Z|J|10|1|11]]|A|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@$I|13|J|14|1|15]]|A|$]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]]]

By default Spring Boot gives json with error details.

<pre><code>curl -v localhost:8080/greet | json_pp
[...]
&lt; HTTP/1.1 400 Bad Request
[...]
{
 "timestamp" : 1413313361387,
 "exception" : "org.springframework.web.bind.MissingServletRequestParameterException",
 "status" : 400,
 "error" : "Bad Request",
 "path" : "/greet",
 "message" : "Required String parameter 'name' is not present"
}
</code></pre>

It also works for all kind of request mapping errors. Check this article
<a href="http://www.jayway.com/2014/10/19/spring-boot-error-responses/" rel="noreferrer">http://www.jayway.com/2014/10/19/spring-boot-error-responses/</a>

If you want to create log it to NoSQL. You can create @ControllerAdvice where you would log it and then re-throw the exception. 
There is example in documentation
<a href="https://spring.io/blog/2013/11/01/exception-handling-in-spring-mvc" rel="noreferrer">https://spring.io/blog/2013/11/01/exception-handling-in-spring-mvc</a>

blocks|key|137954|text|新答案(2016-04-20)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|137955|使用Spring+Boot+1.3.1版本|137956|新步骤1+-向application.properties添加以下属性很容易，而且干扰较少：|137957|spring.mvc.throw-exception-if-no-handler-found=true
spring.resources.add-mappings=false|code-block|syntax|javascript|137958|137959|比修改现有的DispatcherServlet实例容易得多(如下所示)！-+JO‘|blockquote|137960|137961|137962|如果使用完整的RESTful应用程序，禁用静态资源的自动映射是非常重要的，因为如果您使用Spring+Boot的默认配置来处理静态资源，那么资源处理程序将处理请求(它是最后排序的，并映射到/**，这意味着它会拾取应用程序中任何其他处理程序都没有处理过的请求)，这样dispatcher+servlet就不会抛出异常。|137963|137964|新答案(2015-12-04)|137965|使用Spring+Boot+1.2.7.RELEASE|137966|新步骤1+-我发现了一种侵入性小得多的设置"throExceptionIfNoHandlerFound“标志的方法。将下面的DispatcherServlet替换代码(步骤1)替换为您的应用程序初始化类中的代码：|137967|@ComponentScan()
@EnableAutoConfiguration
public+class+MyApplication+extends+SpringBootServletInitializer+{
++++private+static+Logger+LOG+=+LoggerFactory.getLogger(MyApplication.class);
++++public+static+void+main(String[]+args)+{
++++++++ApplicationContext+ctx+=+SpringApplication.run(MyApplication.class,+args);
++++++++DispatcherServlet+dispatcherServlet+=+(DispatcherServlet)ctx.getBean("dispatcherServlet");
++++++++dispatcherServlet.setThrowExceptionIfNoHandlerFound(true);
++++}|137968|在本例中，我们在现有的DispatcherServlet上设置了该标志，它保留了Spring+Boot框架所做的任何自动配置。|137969|我还发现了另一件事--+@EnableWebMvc注释对Spring+Boot来说是致命的。是的，该注释能够捕获下面描述的所有控制器异常，但它也取消了Spring+Boot通常提供的许多有用的自动配置。在使用Spring+Boot时，要非常小心地使用该注释。|137970|137971|原始答案：|137972|经过更多的研究和对这里发布的解决方案的跟进(感谢您的帮助！)并且在Spring代码中进行了大量的运行时跟踪，我最终找到了一个可以处理所有异常(不是错误，但请继续阅读)的配置，包括404。|137973|MVC步骤1+-告诉SpringBoot在“找不到处理程序”的情况下停止使用。我们希望Spring抛出一个异常，而不是向客户端返回一个重定向到"/error“的视图。为此，您需要在其中一个配置类中有一个条目：|137974|//+NEW+CODE+ABOVE+REPLACES+THIS!+(2015-12-04)
@Configuration
public+class+MyAppConfig+{
++++@Bean++//+Magic+entry+
++++public+DispatcherServlet+dispatcherServlet()+{
++++++++DispatcherServlet+ds+=+new+DispatcherServlet();
++++++++ds.setThrowExceptionIfNoHandlerFound(true);
++++++++return+ds;
++++}
}|137975|这样做的缺点是它取代了默认的dispatcher+servlet。这对我们来说还不是问题，没有出现副作用或执行问题。如果您出于其他原因要使用dispatcher+servlet做任何其他事情，那么这里就是您要做的地方。|137976|步骤2+-现在spring+boot将在找不到处理程序时抛出异常，该异常可以在统一的异常处理程序中与任何其他异常处理程序一起处理：|137977|@EnableWebMvc
@ControllerAdvice
public+class+ServiceExceptionHandler+extends+ResponseEntityExceptionHandler+{

++++@ExceptionHandler(Throwable.class)
++++@ResponseBody
++++ResponseEntity<Object>+handleControllerException(HttpServletRequest+req,+Throwable+ex)+{
++++++++ErrorResponse+errorResponse+=+new+ErrorResponse(ex);
++++++++if(ex+instanceof+ServiceException)+{
++++++++++++errorResponse.setDetails(((ServiceException)ex).getDetails());
++++++++}
++++++++if(ex+instanceof+ServiceHttpException)+{
++++++++++++return+new+ResponseEntity<Object>(errorResponse,((ServiceHttpException)ex).getStatus());
++++++++}+else+{
++++++++++++return+new+ResponseEntity<Object>(errorResponse,HttpStatus.INTERNAL_SERVER_ERROR);
++++++++}
++++}

++++@Override
++++protected+ResponseEntity<Object>+handleNoHandlerFoundException(NoHandlerFoundException+ex,+HttpHeaders+headers,+HttpStatus+status,+WebRequest+request)+{
++++++++Map<String,String>+responseBody+=+new+HashMap<>();
++++++++responseBody.put("path",request.getContextPath());
++++++++responseBody.put("message","The+URL+you+have+reached+is+not+in+service+at+this+time+(404).");
++++++++return+new+ResponseEntity<Object>(responseBody,HttpStatus.NOT_FOUND);
++++}
++++...
}|137978|请记住，我认为"@EnableWebMvc“注释在这里很重要。这一切似乎都离不开它。仅此而已-您的Spring启动应用程序现在将捕获上述处理程序类中的所有异常，包括404，您可以随心所欲地处理它们。|137979|最后一点-似乎没有一种方法可以让它捕获抛出的错误。我有一个奇怪的想法，就是使用方面来捕获错误，并将它们转换为异常，然后上面的代码就可以处理它们，但我还没有时间真正尝试实现它。希望这对某些人有帮助。|137980|任何意见/更正/增强将不胜感激。|137981|entityMap^0|0|F|0|0|0|6|0|0|0|0|0|0|0|0|0|F|0|0|0|6|0|0|0|0|0|0|5|0|0|12|1U|0|0|0|31|0|0|1T|0|0|0|2R|0|0|2Q|0|0|G|0^^$0|@$1|2|3|4|5|6|7|1W|8|@$9|1X|A|1Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|20|8|@$9|21|A|22|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|23|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|24|8|@]|D|@]|E|$]]|$1|P|3|Q|5|R|7|25|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|26|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|27|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|28|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|29|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|2A|8|@$9|2B|A|2C|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|2D|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|2E|8|@$9|2F|A|2G|B|C]]|D|@]|E|$]]|$1|13|3|14|5|L|7|2H|8|@]|D|@]|E|$M|N]]|$1|15|3|16|5|6|7|2I|8|@]|D|@]|E|$]]|$1|17|3|18|5|6|7|2J|8|@]|D|@]|E|$]]|$1|19|3|-4|5|6|7|2K|8|@]|D|@]|E|$]]|$1|1A|3|1B|5|6|7|2L|8|@$9|2M|A|2N|B|C]]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|2O|8|@]|D|@]|E|$]]|$1|1E|3|1F|5|6|7|2P|8|@$9|2Q|A|2R|B|C]]|D|@]|E|$]]|$1|1G|3|1H|5|L|7|2S|8|@]|D|@]|E|$M|N]]|$1|1I|3|1J|5|6|7|2T|8|@$9|2U|A|2V|B|C]]|D|@]|E|$]]|$1|1K|3|1L|5|6|7|2W|8|@$9|2X|A|2Y|B|C]]|D|@]|E|$]]|$1|1M|3|1N|5|L|7|2Z|8|@]|D|@]|E|$M|N]]|$1|1O|3|1P|5|6|7|30|8|@$9|31|A|32|B|C]]|D|@]|E|$]]|$1|1Q|3|1R|5|6|7|33|8|@$9|34|A|35|B|C]]|D|@]|E|$]]|$1|1S|3|1T|5|6|7|36|8|@$9|37|A|38|B|C]]|D|@]|E|$]]|$1|1U|3|-4|5|6|7|39|8|@]|D|@]|E|$]]]|1V|$]]

New answer (2016-04-20)

Using Spring Boot 1.3.1.RELEASE

New Step 1 - It is easy and less intrusive to add the following properties to the application.properties:

<pre><code>spring.mvc.throw-exception-if-no-handler-found=true
spring.resources.add-mappings=false
</code></pre>

<blockquote>
 Much easier than modifying the existing DispatcherServlet instance (as below)! - JO'
</blockquote>

If working with a full RESTful Application, it is very important to disable the automatic mapping of static resources since if you are using Spring Boot's default configuration for handling static resources then the resource handler will be handling the request (it's ordered last and mapped to /** which means that it picks up any requests that haven't been handled by any other handler in the application) so the dispatcher servlet doesn't get a chance to throw an exception.

<hr>

New Answer (2015-12-04)

Using Spring Boot 1.2.7.RELEASE

New Step 1 - I found a much less intrusive way of setting the "throExceptionIfNoHandlerFound" flag. Replace the DispatcherServlet replacement code below (Step 1) with this in your application initialization class:

<pre><code>@ComponentScan()
@EnableAutoConfiguration
public class MyApplication extends SpringBootServletInitializer {
 private static Logger LOG = LoggerFactory.getLogger(MyApplication.class);
 public static void main(String[] args) {
 ApplicationContext ctx = SpringApplication.run(MyApplication.class, args);
 DispatcherServlet dispatcherServlet = (DispatcherServlet)ctx.getBean("dispatcherServlet");
 dispatcherServlet.setThrowExceptionIfNoHandlerFound(true);
 }
</code></pre>

In this case, we're setting the flag on the existing DispatcherServlet, which preserves any auto-configuration by the Spring Boot framework. 

One more thing I've found - the @EnableWebMvc annotation is deadly to Spring Boot. Yes, that annotation enables things like being able to catch all the controller exceptions as described below, but it also kills a LOT of the helpful auto-configuration that Spring Boot would normally provide. Use that annotation with extreme caution when you use Spring Boot.

<hr>

Original Answer:

After a lot more research and following up on the solutions posted here (thanks for the help!) and no small amount of runtime tracing into the Spring code, I finally found a configuration that will handle all Exceptions (not Errors, but read on) including 404s.

Step 1 - tell SpringBoot to stop using MVC for "handler not found" situations. We want Spring to throw an exception instead of returning to the client a view redirect to "/error". To do this, you need to have an entry in one of your configuration classes:

<pre><code>// NEW CODE ABOVE REPLACES THIS! (2015-12-04)
@Configuration
public class MyAppConfig {
 @Bean // Magic entry 
 public DispatcherServlet dispatcherServlet() {
 DispatcherServlet ds = new DispatcherServlet();
 ds.setThrowExceptionIfNoHandlerFound(true);
 return ds;
 }
}
</code></pre>

The downside of this is that it replaces the default dispatcher servlet. This hasn't been a problem for us yet, with no side effects or execution problems showing up. If you're going to do anything else with the dispatcher servlet for other reasons, this is the place to do them.

Step 2 - Now that spring boot will throw an exception when no handler is found, that exception can be handled with any others in a unified exception handler:

<pre><code>@EnableWebMvc
@ControllerAdvice
public class ServiceExceptionHandler extends ResponseEntityExceptionHandler {

 @ExceptionHandler(Throwable.class)
 @ResponseBody
 ResponseEntity&lt;Object&gt; handleControllerException(HttpServletRequest req, Throwable ex) {
 ErrorResponse errorResponse = new ErrorResponse(ex);
 if(ex instanceof ServiceException) {
 errorResponse.setDetails(((ServiceException)ex).getDetails());
 }
 if(ex instanceof ServiceHttpException) {
 return new ResponseEntity&lt;Object&gt;(errorResponse,((ServiceHttpException)ex).getStatus());
 } else {
 return new ResponseEntity&lt;Object&gt;(errorResponse,HttpStatus.INTERNAL_SERVER_ERROR);
 }
 }

 @Override
 protected ResponseEntity&lt;Object&gt; handleNoHandlerFoundException(NoHandlerFoundException ex, HttpHeaders headers, HttpStatus status, WebRequest request) {
 Map&lt;String,String&gt; responseBody = new HashMap&lt;&gt;();
 responseBody.put("path",request.getContextPath());
 responseBody.put("message","The URL you have reached is not in service at this time (404).");
 return new ResponseEntity&lt;Object&gt;(responseBody,HttpStatus.NOT_FOUND);
 }
 ...
}
</code></pre>

Keep in mind that I think the "@EnableWebMvc" annotation is significant here. It seems that none of this works without it. And that's it - your Spring boot app will now catch all exceptions, including 404s, in the above handler class and you may do with them as you please.

One last point - there doesn't seem to be a way to get this to catch thrown Errors. I have a wacky idea of using aspects to catch errors and turn them into Exceptions that the above code can then deal with, but I have not yet had time to actually try implementing that. Hope this helps someone.

Any comments/corrections/enhancements will be appreciated.

blocks|key|139355|text|使用dispatcherServlet.setThrowExceptionIfNoHandlerFound(true);和@EnableWebMvc+@ControllerAdvice的解决方案适用于我在Spring+Boot1.3.1上工作，而不是在1.2.7上工作|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|139356|entityMap^0|2|1M|1P|V|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Solution with 
<code>dispatcherServlet.setThrowExceptionIfNoHandlerFound(true);</code> and
<code>@EnableWebMvc
@ControllerAdvice</code>
worked for me with Spring Boot 1.3.1, while was not working on 1.2.7

blocks|key|141493|text|这段代码怎么样？我使用回退请求映射来捕获404个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141494|@Controller
@ControllerAdvice
public+class+ExceptionHandlerController+{

++++@ExceptionHandler(Exception.class)
++++public+ModelAndView+exceptionHandler(HttpServletRequest+request,+HttpServletResponse+response,+Exception+ex)+{
++++++++//If+exception+has+a+ResponseStatus+annotation+then+use+its+response+code
++++++++ResponseStatus+responseStatusAnnotation+=+AnnotationUtils.findAnnotation(ex.getClass(),+ResponseStatus.class);

++++++++return+buildModelAndViewErrorPage(request,+response,+ex,+responseStatusAnnotation+!=+null+?+responseStatusAnnotation.value()+:+HttpStatus.INTERNAL_SERVER_ERROR);
++++}

++++@RequestMapping("*")
++++public+ModelAndView+fallbackHandler(HttpServletRequest+request,+HttpServletResponse+response)+throws+Exception+{
++++++++return+buildModelAndViewErrorPage(request,+response,+null,+HttpStatus.NOT_FOUND);
++++}

++++private+ModelAndView+buildModelAndViewErrorPage(HttpServletRequest+request,+HttpServletResponse+response,+Exception+ex,+HttpStatus+httpStatus)+{
++++++++response.setStatus(httpStatus.value());

++++++++ModelAndView+mav+=+new+ModelAndView("error.html");
++++++++if+(ex+!=+null)+{
++++++++++++mav.addObject("title",+ex);
++++++++}
++++++++mav.addObject("content",+request.getRequestURL());
++++++++return+mav;
++++}

}|code-block|syntax|javascript|141495|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

What about this code ? I use a fallback request mapping to catch 404 errors.

<pre><code>@Controller
@ControllerAdvice
public class ExceptionHandlerController {

 @ExceptionHandler(Exception.class)
 public ModelAndView exceptionHandler(HttpServletRequest request, HttpServletResponse response, Exception ex) {
 //If exception has a ResponseStatus annotation then use its response code
 ResponseStatus responseStatusAnnotation = AnnotationUtils.findAnnotation(ex.getClass(), ResponseStatus.class);

 return buildModelAndViewErrorPage(request, response, ex, responseStatusAnnotation != null ? responseStatusAnnotation.value() : HttpStatus.INTERNAL_SERVER_ERROR);
 }

 @RequestMapping("*")
 public ModelAndView fallbackHandler(HttpServletRequest request, HttpServletResponse response) throws Exception {
 return buildModelAndViewErrorPage(request, response, null, HttpStatus.NOT_FOUND);
 }

 private ModelAndView buildModelAndViewErrorPage(HttpServletRequest request, HttpServletResponse response, Exception ex, HttpStatus httpStatus) {
 response.setStatus(httpStatus.value());

 ModelAndView mav = new ModelAndView("error.html");
 if (ex != null) {
 mav.addObject("title", ex);
 }
 mav.addObject("content", request.getRequestURL());
 return mav;
 }

}
</code></pre>

blocks|key|140398|text|对于REST控制器，我建议使用Zalando+Problem+Spring+Web。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|140399|https://github.com/zalando/problem-spring-web|140400|如果Spring+Boot的目标是嵌入一些自动配置，那么这个库可以做更多的异常处理。您只需要添加依赖项：|140401|<dependency>
++++<groupId>org.zalando</groupId>
++++<artifactId>problem-spring-web</artifactId>
++++<version>LATEST</version>
</dependency>|code-block|syntax|javascript|140402|然后为您的异常定义一个或多个建议特征(或使用默认提供的特征)|140403|public+interface+NotAcceptableAdviceTrait+extends+AdviceTrait+{

++++@ExceptionHandler
++++default+ResponseEntity<Problem>+handleMediaTypeNotAcceptable(
++++++++++++final+HttpMediaTypeNotAcceptableException+exception,
++++++++++++final+NativeWebRequest+request)+{
++++++++return+Responses.create(Status.NOT_ACCEPTABLE,+exception,+request);
++++}

}|140404|然后，您可以将异常处理的控制器建议定义为：|140405|@ControllerAdvice
class+ExceptionHandling+implements+MethodNotAllowedAdviceTrait,+NotAcceptableAdviceTrait+{

}|140406|entityMap|0|LINK|mutability|MUTABLE|url^0|F|Q|0|0|19|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1B|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1C|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1D|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|1E|8|@]|D|@]|E|$]]|$1|U|3|V|5|L|7|1F|8|@]|D|@]|E|$M|N]]|$1|W|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|G]]]]

For REST controllers, I would recommend to use <code>Zalando Problem Spring Web</code>.

<a href="https://github.com/zalando/problem-spring-web" rel="nofollow noreferrer">https://github.com/zalando/problem-spring-web</a>

If Spring Boot aims to embed some auto-configuration, this library does more for exception handling. You just need to add the dependency:

<pre><code>&lt;dependency&gt;
 &lt;groupId&gt;org.zalando&lt;/groupId&gt;
 &lt;artifactId&gt;problem-spring-web&lt;/artifactId&gt;
 &lt;version&gt;LATEST&lt;/version&gt;
&lt;/dependency&gt;
</code></pre>

And then define one or more advice traits for your exceptions (or use those provided by default)

<pre><code>public interface NotAcceptableAdviceTrait extends AdviceTrait {

 @ExceptionHandler
 default ResponseEntity&lt;Problem&gt; handleMediaTypeNotAcceptable(
 final HttpMediaTypeNotAcceptableException exception,
 final NativeWebRequest request) {
 return Responses.create(Status.NOT_ACCEPTABLE, exception, request);
 }

}
</code></pre>

Then you can defined the controller advice for exception handling as:

<pre><code>@ControllerAdvice
class ExceptionHandling implements MethodNotAllowedAdviceTrait, NotAcceptableAdviceTrait {

}
</code></pre>

blocks|key|2710874|text|在Spring+Boot+1.4%2B中，添加了新的酷的类来简化异常处理，这有助于删除样板代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2710875|为异常处理提供了一种新的@RestControllerAdvice，它是@ControllerAdvice和@ResponseBody的结合。在使用这个新注释时，可以删除@ExceptionHandler方法上的@ResponseBody。|offset|length|style|CODE|2710876|即|2710877|@RestControllerAdvice
public+class+GlobalControllerExceptionHandler+{

++++@ExceptionHandler(value+=+{+Exception.class+})
++++@ResponseStatus(HttpStatus.INTERNAL_SERVER_ERROR)
++++public+ApiErrorResponse+unknownException(Exception+ex,+WebRequest+req)+{
++++++++return+new+ApiErrorResponse(...);
++++}
}|code-block|syntax|javascript|2710878|为了处理404错误，向application.properties添加@EnableWebMvc注释和以下内容就足够了：|2710879|spring.mvc.throw-exception-if-no-handler-found=true|2710880|你可以在这里找到并使用源代码：|2710881|https://github.com/magiccrafter/spring-boot-exception-handling|2710882|entityMap|0|LINK|mutability|MUTABLE|url^0|0|C|L|10|H|1I|D|2D|H|2Y|D|0|0|0|Z|D|0|0|1F|0|0|0|1Q|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@$D|15|E|16|F|G]|$D|17|E|18|F|G]|$D|19|E|1A|F|G]|$D|1B|E|1C|F|G]|$D|1D|E|1E|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1F|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1G|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1H|8|@$D|1I|E|1J|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1K|8|@$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1N|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1O|8|@]|9|@$D|1P|E|1Q|1|1R]]|A|$]]|$1|W|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|V]]]]

With Spring Boot 1.4+ new cool classes for easier exception handling were added that helps in removing the boilerplate code.

A new <code>@RestControllerAdvice</code> is provided for exception handling, it is combination of <code>@ControllerAdvice</code> and <code>@ResponseBody</code>. You can remove the <code>@ResponseBody</code> on the <code>@ExceptionHandler</code> method when use this new annotation.

i.e. 

<pre><code>@RestControllerAdvice
public class GlobalControllerExceptionHandler {

 @ExceptionHandler(value = { Exception.class })
 @ResponseStatus(HttpStatus.INTERNAL_SERVER_ERROR)
 public ApiErrorResponse unknownException(Exception ex, WebRequest req) {
 return new ApiErrorResponse(...);
 }
}
</code></pre>

For handling 404 errors adding <code>@EnableWebMvc</code> annotation and the following to application.properties was enough: 
<code>spring.mvc.throw-exception-if-no-handler-found=true</code>

You can find and play with the sources here: 
<a href="https://github.com/magiccrafter/spring-boot-exception-handling">https://github.com/magiccrafter/spring-boot-exception-handling</a>

blocks|key|139414|text|虽然这是一个较老的问题，但我想分享我对此的看法。我希望，这会对你们中的一些人有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|139415|我目前正在构建一个REST+API，它使用Spring+Boot+1.5.2.RELEASE和Spring+Framework+4.3.7.RELEASE。我使用Java配置方法(而不是XML配置)。另外，我的项目使用了使用@RestControllerAdvice注释的全局异常处理机制(见下文)。|offset|length|style|CODE|139416|我的项目与您的项目具有相同的要求:当客户端尝试向不存在的HTTP+404+Not+Found发送请求时，我希望REST+API在HTTP响应中返回一个带有JSON有效负载的URL。在我的示例中，JSON有效负载如下所示(这与Spring+Boot默认设置btw明显不同)：|139417|{
++++"code":+1000,
++++"message":+"No+handler+found+for+your+request.",
++++"timestamp":+"2017-11-20T02:40:57.628Z"
}|code-block|syntax|javascript|139418|我终于让它工作了。以下是您需要简要完成的主要任务：|139419|139420|确保在API客户端调用不存在处理程序方法的URLS时抛出NoHandlerFoundException+(请参见下面的步骤1)。|unordered-list-item|139421|创建一个自定义错误类(在我的示例中为ApiError)，其中包含应返回给API客户端的所有数据(请参见步骤2)。|139422|创建一个异常处理程序，该处理程序在NoHandlerFoundException上进行反应并向API客户端返回正确的错误消息(请参阅步骤3)。<代码>H212<代码>H113为其编写测试并确保其正常工作(请参见步骤4)。<代码>H214<代码>F215|139423|139424|好的，现在来看细节：|139425|第1步:配置application.properties|BOLD|139426|我必须将以下两个配置设置添加到项目的application.properties文件中：|139427|spring.mvc.throw-exception-if-no-handler-found=true
spring.resources.add-mappings=false|139428|这确保了，在客户端试图访问不存在能够处理请求的控制器方法的情况下，将抛出NoHandlerFoundException。|139429|第2步:为错误创建类|139430|我在Eugen+Paraschiv的博客上做了一个类似于this+article中建议的类。此类表示API错误。如果出现错误，此信息将在HTTP响应正文中发送给客户端。|139431|public+class+ApiError+{

++++private+int+code;
++++private+String+message;
++++private+Instant+timestamp;

++++public+ApiError(int+code,+String+message)+{
++++++++this.code+=+code;
++++++++this.message+=+message;
++++++++this.timestamp+=+Instant.now();
++++}

++++public+ApiError(int+code,+String+message,+Instant+timestamp)+{
++++++++this.code+=+code;
++++++++this.message+=+message;
++++++++this.timestamp+=+timestamp;
++++}

++++//+Getters+and+setters+here...
}|139432|第3步:创建/配置全局异常处理程序|139433|我使用以下类来处理异常(为简单起见，我删除了import语句、日志记录代码和其他一些不相关的代码)：|139434|@RestControllerAdvice
public+class+GlobalExceptionHandler+{

++++@ExceptionHandler(NoHandlerFoundException.class)
++++@ResponseStatus(HttpStatus.NOT_FOUND)
++++public+ApiError+noHandlerFoundException(
++++++++++++NoHandlerFoundException+ex)+{

++++++++int+code+=+1000;
++++++++String+message+=+"No+handler+found+for+your+request.";
++++++++return+new+ApiError(code,+message);
++++}

++++//+More+exception+handlers+here+...
}|139435|第4步:编写测试|139436|我希望确保API始终向调用客户端返回正确的错误消息，即使在失败的情况下也是如此。因此，我写了一个这样的测试：|139437|@RunWith(SpringRunner.class)
@SpringBootTest(webEnvironment+=+SprintBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureMockMvc
@ActiveProfiles("dev")
public+class+GlobalExceptionHandlerIntegrationTest+{

++++public+static+final+String+ISO8601_DATE_REGEX+=
++++++++"%5E\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}\\.\\d{3}Z$";

++++@Autowired
++++private+MockMvc+mockMvc;

++++@Test
++++@WithMockUser(roles+=+"DEVICE_SCAN_HOSTS")
++++public+void+invalidUrl_returnsHttp404()+throws+Exception+{
++++++++RequestBuilder+requestBuilder+=+getGetRequestBuilder("/does-not-exist");
++++++++mockMvc.perform(requestBuilder)
++++++++++++.andExpect(status().isNotFound())
++++++++++++.andExpect(jsonPath("$.code",+is(1000)))
++++++++++++.andExpect(jsonPath("$.message",+is("No+handler+found+for+your+request.")))
++++++++++++.andExpect(jsonPath("$.timestamp",+RegexMatcher.matchesRegex(ISO8601_DATE_REGEX)));
++++}

++++private+RequestBuilder+getGetRequestBuilder(String+url)+{
++++++++return+MockMvcRequestBuilders
++++++++++++.get(url)
++++++++++++.accept(MediaType.APPLICATION_JSON);
++++}|139438|可以不使用@ActiveProfiles("dev")注释。我只在使用不同的配置文件时才使用它。RegexMatcher是我用来更好地处理时间戳字段的自定义Hamcrest+matcher。下面是代码(我发现它是here)：|139439|public+class+RegexMatcher+extends+TypeSafeMatcher<String>+{

++++private+final+String+regex;

++++public+RegexMatcher(final+String+regex)+{
++++++++this.regex+=+regex;
++++}

++++@Override
++++public+void+describeTo(final+Description+description)+{
++++++++description.appendText("matches+regular+expression=`"+%2B+regex+%2B+"`");
++++}

++++@Override
++++public+boolean+matchesSafely(final+String+string)+{
++++++++return+string.matches(regex);
++++}

++++//+Matcher+method+you+can+call+on+this+matcher+class
++++public+static+RegexMatcher+matchesRegex(final+String+string)+{
++++++++return+new+RegexMatcher(regex);
++++}
}|139440|从我这边一些进一步的注意事项：|139441|139442|在StackOverflow上的许多其他帖子中，人们建议设置@EnableWebMvc注释。在我的例子中，这不是必需的。|139443|这种方法在MockMvc+(参见上面的测试)中工作得很好。|139444|139445|entityMap|0|LINK|mutability|MUTABLE|url|http://www.baeldung.com/global-error-handler-in-a-spring-rest-api|1|http://hamcrest.org/JavaHamcrest/|2|http://www.vogella.com/tutorials/Hamcrest/article.html^0|0|34|L|0|S|I|0|0|0|0|S|N|0|I|8|0|H|N|0|0|0|0|S|0|I|M|0|0|10|N|0|0|5|0|S|C|0|0|0|0|H|0|0|0|0|8|0|0|0|5|M|1C|C|26|G|1|2Y|4|2|0|0|4|B|0|0|U|D|0|0|0^^$0|@$1|2|3|4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2H|8|@$D|2I|E|2J|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|2K|8|@$D|2L|E|2M|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|2N|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|2O|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|2P|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|2Q|8|@$D|2R|E|2S|F|G]]|9|@]|A|$]]|$1|U|3|V|5|T|7|2T|8|@$D|2U|E|2V|F|G]]|9|@]|A|$]]|$1|W|3|X|5|T|7|2W|8|@$D|2X|E|2Y|F|G]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|30|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|31|8|@$D|32|E|33|F|13]]|9|@]|A|$]]|$1|14|3|15|5|6|7|34|8|@$D|35|E|36|F|G]]|9|@]|A|$]]|$1|16|3|17|5|L|7|37|8|@]|9|@]|A|$M|N]]|$1|18|3|19|5|6|7|38|8|@$D|39|E|3A|F|G]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|3B|8|@$D|3C|E|3D|F|13]]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|3E|8|@]|9|@$D|3F|E|3G|1|3H]]|A|$]]|$1|1E|3|1F|5|L|7|3I|8|@]|9|@]|A|$M|N]]|$1|1G|3|1H|5|6|7|3J|8|@$D|3K|E|3L|F|13]]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|3M|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|L|7|3N|8|@]|9|@]|A|$M|N]]|$1|1M|3|1N|5|6|7|3O|8|@$D|3P|E|3Q|F|13]]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3R|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|L|7|3S|8|@]|9|@]|A|$M|N]]|$1|1S|3|1T|5|6|7|3T|8|@$D|3U|E|3V|F|G]|$D|3W|E|3X|F|G]]|9|@$D|3Y|E|3Z|1|40]|$D|41|E|42|1|43]]|A|$]]|$1|1U|3|1V|5|L|7|44|8|@]|9|@]|A|$M|N]]|$1|1W|3|1X|5|6|7|45|8|@$D|46|E|47|F|13]]|9|@]|A|$]]|$1|1Y|3|-4|5|6|7|48|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|T|7|49|8|@$D|4A|E|4B|F|G]]|9|@]|A|$]]|$1|21|3|22|5|T|7|4C|8|@]|9|@]|A|$]]|$1|23|3|-4|5|6|7|4D|8|@]|9|@]|A|$]]|$1|24|3|-4|5|6|7|4E|8|@]|9|@]|A|$]]]|25|$26|$5|27|28|29|A|$2A|2B]]|2C|$5|27|28|29|A|$2A|2D]]|2E|$5|27|28|29|A|$2A|2F]]]]

Although this is an older question, I would like to share my thoughts on this. I hope, that it will be helpful to some of you.

I am currently building a REST API which makes use of Spring Boot 1.5.2.RELEASE with Spring Framework 4.3.7.RELEASE. I use the Java Config approach (as opposed to XML configuration). Also, my project uses a global exception handling mechanism using the <code>@RestControllerAdvice</code> annotation (see later below).

My project has the same requirements as yours: I want my REST API to return a <code>HTTP 404 Not Found</code> with an accompanying JSON payload in the HTTP response to the API client when it tries to send a request to an URL which does not exist. In my case, the JSON payload looks like this (which clearly differs from the Spring Boot default, btw.):

<pre><code>{
 "code": 1000,
 "message": "No handler found for your request.",
 "timestamp": "2017-11-20T02:40:57.628Z"
}
</code></pre>

I finally made it work. Here are the main tasks you need to do in brief:

<ul>
<li>Make sure that the <code>NoHandlerFoundException</code> is thrown if API clients
call URLS for which no handler method exists (see Step 1 below).</li>
<li>Create a custom error class (in my case <code>ApiError</code>) which contains all the data that should be returned to the API client (see step 2).</li>
<li>Create an exception handler which reacts on the <code>NoHandlerFoundException</code>
and returns a proper error message to the API client (see step 3).</li>
<li>Write a test for it and make sure, it works (see step 4).</li>
</ul>

Ok, now on to the details:

Step 1: Configure application.properties

I had to add the following two configuration settings to the project's <code>application.properties</code> file:

<pre><code>spring.mvc.throw-exception-if-no-handler-found=true
spring.resources.add-mappings=false
</code></pre>

This makes sure, the <code>NoHandlerFoundException</code> is thrown in cases where a client tries to access an URL for which no controller method exists which would be able to handle the request.

Step 2: Create a Class for API Errors

I made a class similar to the one suggested in <a href="http://www.baeldung.com/global-error-handler-in-a-spring-rest-api" rel="noreferrer">this article</a> on Eugen Paraschiv's blog. This class represents an API error. This information is 
sent to the client in the HTTP response body in case of an error.

<pre><code>public class ApiError {

 private int code;
 private String message;
 private Instant timestamp;

 public ApiError(int code, String message) {
 this.code = code;
 this.message = message;
 this.timestamp = Instant.now();
 }

 public ApiError(int code, String message, Instant timestamp) {
 this.code = code;
 this.message = message;
 this.timestamp = timestamp;
 }

 // Getters and setters here...
}
</code></pre>

Step 3: Create / Configure a Global Exception Handler

I use the following class to handle exceptions (for simplicity, I have removed import statements, logging code and some other, non-relevant pieces of code):

<pre><code>@RestControllerAdvice
public class GlobalExceptionHandler {

 @ExceptionHandler(NoHandlerFoundException.class)
 @ResponseStatus(HttpStatus.NOT_FOUND)
 public ApiError noHandlerFoundException(
 NoHandlerFoundException ex) {

 int code = 1000;
 String message = "No handler found for your request.";
 return new ApiError(code, message);
 }

 // More exception handlers here ...
}
</code></pre>

Step 4: Write a test

I want to make sure, the API always returns the correct error messages to the calling client, even in the case of failure. Thus, I wrote a test like this:

<pre><code>@RunWith(SpringRunner.class)
@SpringBootTest(webEnvironment = SprintBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureMockMvc
@ActiveProfiles("dev")
public class GlobalExceptionHandlerIntegrationTest {

 public static final String ISO8601_DATE_REGEX =
 "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}\\.\\d{3}Z$";

 @Autowired
 private MockMvc mockMvc;

 @Test
 @WithMockUser(roles = "DEVICE_SCAN_HOSTS")
 public void invalidUrl_returnsHttp404() throws Exception {
 RequestBuilder requestBuilder = getGetRequestBuilder("/does-not-exist");
 mockMvc.perform(requestBuilder)
 .andExpect(status().isNotFound())
 .andExpect(jsonPath("$.code", is(1000)))
 .andExpect(jsonPath("$.message", is("No handler found for your request.")))
 .andExpect(jsonPath("$.timestamp", RegexMatcher.matchesRegex(ISO8601_DATE_REGEX)));
 }

 private RequestBuilder getGetRequestBuilder(String url) {
 return MockMvcRequestBuilders
 .get(url)
 .accept(MediaType.APPLICATION_JSON);
 }
</code></pre>

The <code>@ActiveProfiles("dev")</code> annotation can be left away. I use it only as I work with different profiles. The <code>RegexMatcher</code> is a custom <a href="http://hamcrest.org/JavaHamcrest/" rel="noreferrer">Hamcrest matcher</a> I use to better handle timestamp fields. Here's the code (I found it <a href="http://www.vogella.com/tutorials/Hamcrest/article.html" rel="noreferrer">here</a>):

<pre><code>public class RegexMatcher extends TypeSafeMatcher&lt;String&gt; {

 private final String regex;

 public RegexMatcher(final String regex) {
 this.regex = regex;
 }

 @Override
 public void describeTo(final Description description) {
 description.appendText("matches regular expression=`" + regex + "`");
 }

 @Override
 public boolean matchesSafely(final String string) {
 return string.matches(regex);
 }

 // Matcher method you can call on this matcher class
 public static RegexMatcher matchesRegex(final String string) {
 return new RegexMatcher(regex);
 }
}
</code></pre>

Some further notes from my side:

<ul>
<li>In many other posts on StackOverflow, people suggested setting the <code>@EnableWebMvc</code> annotation. This was not necessary in my case.</li>
<li>This approach works well with MockMvc (see test above).</li>
</ul>

blocks|key|139450|text|@RestControllerAdvice是Spring+Framework4.3的一个新特性，用于通过横切关注点解决方案处理RestfulApi异常：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|139451|+package+com.khan.vaquar.exception;

import+javax.servlet.http.HttpServletRequest;

import+org.owasp.esapi.errors.IntrusionException;
import+org.owasp.esapi.errors.ValidationException;
import+org.slf4j.Logger;
import+org.slf4j.LoggerFactory;
import+org.springframework.http.HttpStatus;
import+org.springframework.web.bind.MissingServletRequestParameterException;
import+org.springframework.web.bind.annotation.ExceptionHandler;
import+org.springframework.web.bind.annotation.ResponseStatus;
import+org.springframework.web.bind.annotation.RestControllerAdvice;
import+org.springframework.web.servlet.NoHandlerFoundException;

import+com.fasterxml.jackson.core.JsonProcessingException;
import+com.khan.vaquar.domain.ErrorResponse;

/**
+*+Handles+exceptions+raised+through+requests+to+spring+controllers.
+**/
@RestControllerAdvice
public+class+RestExceptionHandler+{

++++private+static+final+String+TOKEN_ID+=+"tokenId";

++++private+static+final+Logger+log+=+LoggerFactory.getLogger(RestExceptionHandler.class);

++++/**
+++++*+Handles+InstructionExceptions+from+the+rest+controller.
+++++*+
+++++*+@param+e+IntrusionException
+++++*+@return+error+response+POJO
+++++*/
++++@ResponseStatus(HttpStatus.BAD_REQUEST)
++++@ExceptionHandler(value+=+IntrusionException.class)
++++public+ErrorResponse+handleIntrusionException(HttpServletRequest+request,+IntrusionException+e)+{+++++++
++++++++log.warn(e.getLogMessage(),+e);
++++++++return+this.handleValidationException(request,+new+ValidationException(e.getUserMessage(),+e.getLogMessage()));
++++}

++++/**
+++++*+Handles+ValidationExceptions+from+the+rest+controller.
+++++*+
+++++*+@param+e+ValidationException
+++++*+@return+error+response+POJO
+++++*/
++++@ResponseStatus(HttpStatus.BAD_REQUEST)
++++@ExceptionHandler(value+=+ValidationException.class)
++++public+ErrorResponse+handleValidationException(HttpServletRequest+request,+ValidationException+e)+{+++++
++++++++String+tokenId+=+request.getParameter(TOKEN_ID);
++++++++log.info(e.getMessage(),+e);

++++++++if+(e.getUserMessage().contains("Token+ID"))+{
++++++++++++tokenId+=+"<OMITTED>";
++++++++}

++++++++return+new+ErrorResponse(+++tokenId,
++++++++++++++++++++++++++++++++++++HttpStatus.BAD_REQUEST.value(),+
++++++++++++++++++++++++++++++++++++e.getClass().getSimpleName(),
++++++++++++++++++++++++++++++++++++e.getUserMessage());
++++}

++++/**
+++++*+Handles+JsonProcessingExceptions+from+the+rest+controller.
+++++*+
+++++*+@param+e+JsonProcessingException
+++++*+@return+error+response+POJO
+++++*/
++++@ResponseStatus(HttpStatus.BAD_REQUEST)
++++@ExceptionHandler(value+=+JsonProcessingException.class)
++++public+ErrorResponse+handleJsonProcessingException(HttpServletRequest+request,+JsonProcessingException+e)+{+++++
++++++++String+tokenId+=+request.getParameter(TOKEN_ID);
++++++++log.info(e.getMessage(),+e);
++++++++return+new+ErrorResponse(+++tokenId,
++++++++++++++++++++++++++++++++++++HttpStatus.BAD_REQUEST.value(),+
++++++++++++++++++++++++++++++++++++e.getClass().getSimpleName(),
++++++++++++++++++++++++++++++++++++e.getOriginalMessage());
++++}

++++/**
+++++*+Handles+IllegalArgumentExceptions+from+the+rest+controller.
+++++*+
+++++*+@param+e+IllegalArgumentException
+++++*+@return+error+response+POJO
+++++*/
++++@ResponseStatus(HttpStatus.BAD_REQUEST)
++++@ExceptionHandler(value+=+IllegalArgumentException.class)
++++public+ErrorResponse+handleIllegalArgumentException(HttpServletRequest+request,+IllegalArgumentException+e)+{
++++++++String+tokenId+=+request.getParameter(TOKEN_ID);
++++++++log.info(e.getMessage(),+e);
++++++++return+new+ErrorResponse(+++tokenId,
++++++++++++++++++++++++++++++++++++HttpStatus.BAD_REQUEST.value(),+
++++++++++++++++++++++++++++++++++++e.getClass().getSimpleName(),+
++++++++++++++++++++++++++++++++++++e.getMessage());
++++}

++++@ResponseStatus(HttpStatus.BAD_REQUEST)
++++@ExceptionHandler(value+=+UnsupportedOperationException.class)
++++public+ErrorResponse+handleUnsupportedOperationException(HttpServletRequest+request,+UnsupportedOperationException+e)+{
++++++++String+tokenId+=+request.getParameter(TOKEN_ID);
++++++++log.info(e.getMessage(),+e);
++++++++return+new+ErrorResponse(+++tokenId,
++++++++++++++++++++++++++++++++++++HttpStatus.BAD_REQUEST.value(),+
++++++++++++++++++++++++++++++++++++e.getClass().getSimpleName(),+
++++++++++++++++++++++++++++++++++++e.getMessage());
++++}

++++/**
+++++*+Handles+MissingServletRequestParameterExceptions+from+the+rest+controller.
+++++*+
+++++*+@param+e+MissingServletRequestParameterException
+++++*+@return+error+response+POJO
+++++*/
++++@ResponseStatus(HttpStatus.BAD_REQUEST)
++++@ExceptionHandler(value+=+MissingServletRequestParameterException.class)
++++public+ErrorResponse+handleMissingServletRequestParameterException(+HttpServletRequest+request,+
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++MissingServletRequestParameterException+e)+{
++++++++String+tokenId+=+request.getParameter(TOKEN_ID);
++++++++log.info(e.getMessage(),+e);
++++++++return+new+ErrorResponse(+++tokenId,
++++++++++++++++++++++++++++++++++++HttpStatus.BAD_REQUEST.value(),+
++++++++++++++++++++++++++++++++++++e.getClass().getSimpleName(),+
++++++++++++++++++++++++++++++++++++e.getMessage());
++++}

++++/**
+++++*+Handles+NoHandlerFoundExceptions+from+the+rest+controller.
+++++*+
+++++*+@param+e+NoHandlerFoundException
+++++*+@return+error+response+POJO
+++++*/
++++@ResponseStatus(HttpStatus.NOT_FOUND)
++++@ExceptionHandler(value+=+NoHandlerFoundException.class)
++++public+ErrorResponse+handleNoHandlerFoundException(HttpServletRequest+request,+NoHandlerFoundException+e)+{
++++++++String+tokenId+=+request.getParameter(TOKEN_ID);
++++++++log.info(e.getMessage(),+e);
++++++++return+new+ErrorResponse(+++tokenId,
++++++++++++++++++++++++++++++++++++HttpStatus.NOT_FOUND.value(),+
++++++++++++++++++++++++++++++++++++e.getClass().getSimpleName(),+
++++++++++++++++++++++++++++++++++++"The+resource+"+%2B+e.getRequestURL()+%2B+"+is+unavailable");
++++}

++++/**
+++++*+Handles+all+remaining+exceptions+from+the+rest+controller.
+++++*+
+++++*+This+acts+as+a+catch-all+for+any+exceptions+not+handled+by+previous+exception+handlers.
+++++*+
+++++*+@param+e+Exception
+++++*+@return+error+response+POJO
+++++*/
++++@ResponseStatus(HttpStatus.INTERNAL_SERVER_ERROR)
++++@ExceptionHandler(value+=+Exception.class)
++++public+ErrorResponse+handleException(HttpServletRequest+request,+Exception+e)+{
++++++++String+tokenId+=+request.getParameter(TOKEN_ID);
++++++++log.error(e.getMessage(),+e);
++++++++return+new+ErrorResponse(+++tokenId,
++++++++++++++++++++++++++++++++++++HttpStatus.INTERNAL_SERVER_ERROR.value(),+
++++++++++++++++++++++++++++++++++++e.getClass().getSimpleName(),+
++++++++++++++++++++++++++++++++++++"An+internal+error+occurred");
++++}+++

}|code-block|syntax|javascript|139452|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

@RestControllerAdvice is a new feature of Spring Framework 4.3 to handle Exception with RestfulApi by a cross-cutting concern solution:

<pre><code> package com.khan.vaquar.exception;

import javax.servlet.http.HttpServletRequest;

import org.owasp.esapi.errors.IntrusionException;
import org.owasp.esapi.errors.ValidationException;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.http.HttpStatus;
import org.springframework.web.bind.MissingServletRequestParameterException;
import org.springframework.web.bind.annotation.ExceptionHandler;
import org.springframework.web.bind.annotation.ResponseStatus;
import org.springframework.web.bind.annotation.RestControllerAdvice;
import org.springframework.web.servlet.NoHandlerFoundException;

import com.fasterxml.jackson.core.JsonProcessingException;
import com.khan.vaquar.domain.ErrorResponse;

/**
 * Handles exceptions raised through requests to spring controllers.
 **/
@RestControllerAdvice
public class RestExceptionHandler {

 private static final String TOKEN_ID = "tokenId";

 private static final Logger log = LoggerFactory.getLogger(RestExceptionHandler.class);

 /**
 * Handles InstructionExceptions from the rest controller.
 * 
 * @param e IntrusionException
 * @return error response POJO
 */
 @ResponseStatus(HttpStatus.BAD_REQUEST)
 @ExceptionHandler(value = IntrusionException.class)
 public ErrorResponse handleIntrusionException(HttpServletRequest request, IntrusionException e) { 
 log.warn(e.getLogMessage(), e);
 return this.handleValidationException(request, new ValidationException(e.getUserMessage(), e.getLogMessage()));
 }

 /**
 * Handles ValidationExceptions from the rest controller.
 * 
 * @param e ValidationException
 * @return error response POJO
 */
 @ResponseStatus(HttpStatus.BAD_REQUEST)
 @ExceptionHandler(value = ValidationException.class)
 public ErrorResponse handleValidationException(HttpServletRequest request, ValidationException e) { 
 String tokenId = request.getParameter(TOKEN_ID);
 log.info(e.getMessage(), e);

 if (e.getUserMessage().contains("Token ID")) {
 tokenId = "&lt;OMITTED&gt;";
 }

 return new ErrorResponse( tokenId,
 HttpStatus.BAD_REQUEST.value(), 
 e.getClass().getSimpleName(),
 e.getUserMessage());
 }

 /**
 * Handles JsonProcessingExceptions from the rest controller.
 * 
 * @param e JsonProcessingException
 * @return error response POJO
 */
 @ResponseStatus(HttpStatus.BAD_REQUEST)
 @ExceptionHandler(value = JsonProcessingException.class)
 public ErrorResponse handleJsonProcessingException(HttpServletRequest request, JsonProcessingException e) { 
 String tokenId = request.getParameter(TOKEN_ID);
 log.info(e.getMessage(), e);
 return new ErrorResponse( tokenId,
 HttpStatus.BAD_REQUEST.value(), 
 e.getClass().getSimpleName(),
 e.getOriginalMessage());
 }

 /**
 * Handles IllegalArgumentExceptions from the rest controller.
 * 
 * @param e IllegalArgumentException
 * @return error response POJO
 */
 @ResponseStatus(HttpStatus.BAD_REQUEST)
 @ExceptionHandler(value = IllegalArgumentException.class)
 public ErrorResponse handleIllegalArgumentException(HttpServletRequest request, IllegalArgumentException e) {
 String tokenId = request.getParameter(TOKEN_ID);
 log.info(e.getMessage(), e);
 return new ErrorResponse( tokenId,
 HttpStatus.BAD_REQUEST.value(), 
 e.getClass().getSimpleName(), 
 e.getMessage());
 }

 @ResponseStatus(HttpStatus.BAD_REQUEST)
 @ExceptionHandler(value = UnsupportedOperationException.class)
 public ErrorResponse handleUnsupportedOperationException(HttpServletRequest request, UnsupportedOperationException e) {
 String tokenId = request.getParameter(TOKEN_ID);
 log.info(e.getMessage(), e);
 return new ErrorResponse( tokenId,
 HttpStatus.BAD_REQUEST.value(), 
 e.getClass().getSimpleName(), 
 e.getMessage());
 }

 /**
 * Handles MissingServletRequestParameterExceptions from the rest controller.
 * 
 * @param e MissingServletRequestParameterException
 * @return error response POJO
 */
 @ResponseStatus(HttpStatus.BAD_REQUEST)
 @ExceptionHandler(value = MissingServletRequestParameterException.class)
 public ErrorResponse handleMissingServletRequestParameterException( HttpServletRequest request, 
 MissingServletRequestParameterException e) {
 String tokenId = request.getParameter(TOKEN_ID);
 log.info(e.getMessage(), e);
 return new ErrorResponse( tokenId,
 HttpStatus.BAD_REQUEST.value(), 
 e.getClass().getSimpleName(), 
 e.getMessage());
 }

 /**
 * Handles NoHandlerFoundExceptions from the rest controller.
 * 
 * @param e NoHandlerFoundException
 * @return error response POJO
 */
 @ResponseStatus(HttpStatus.NOT_FOUND)
 @ExceptionHandler(value = NoHandlerFoundException.class)
 public ErrorResponse handleNoHandlerFoundException(HttpServletRequest request, NoHandlerFoundException e) {
 String tokenId = request.getParameter(TOKEN_ID);
 log.info(e.getMessage(), e);
 return new ErrorResponse( tokenId,
 HttpStatus.NOT_FOUND.value(), 
 e.getClass().getSimpleName(), 
 "The resource " + e.getRequestURL() + " is unavailable");
 }

 /**
 * Handles all remaining exceptions from the rest controller.
 * 
 * This acts as a catch-all for any exceptions not handled by previous exception handlers.
 * 
 * @param e Exception
 * @return error response POJO
 */
 @ResponseStatus(HttpStatus.INTERNAL_SERVER_ERROR)
 @ExceptionHandler(value = Exception.class)
 public ErrorResponse handleException(HttpServletRequest request, Exception e) {
 String tokenId = request.getParameter(TOKEN_ID);
 log.error(e.getMessage(), e);
 return new ErrorResponse( tokenId,
 HttpStatus.INTERNAL_SERVER_ERROR.value(), 
 e.getClass().getSimpleName(), 
 "An internal error occurred");
 } 

}
</code></pre>

blocks|key|140443|text|对于希望根据http状态码响应的用户，可以使用ErrorController的方式：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|140444|@Controller
public+class+CustomErrorController+extends+BasicErrorController+{

++++public+CustomErrorController(ServerProperties+serverProperties)+{
++++++++super(new+DefaultErrorAttributes(),+serverProperties.getError());
++++}

++++@Override
++++public+ResponseEntity+error(HttpServletRequest+request)+{
++++++++HttpStatus+status+=+getStatus(request);
++++++++if+(status.equals(HttpStatus.INTERNAL_SERVER_ERROR)){
++++++++++++return+ResponseEntity.status(status).body(ResponseBean.SERVER_ERROR);
++++++++}else+if+(status.equals(HttpStatus.BAD_REQUEST)){
++++++++++++return+ResponseEntity.status(status).body(ResponseBean.BAD_REQUEST);
++++++++}
++++++++return+super.error(request);
++++}
}|code-block|syntax|javascript|140445|这里的ResponseBean是我用于响应的自定义pojo。|140446|entityMap^0|N|F|0|0|3|C|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

For people that want to response according to http status code, you can use the <code>ErrorController</code> way:

<pre><code>@Controller
public class CustomErrorController extends BasicErrorController {

 public CustomErrorController(ServerProperties serverProperties) {
 super(new DefaultErrorAttributes(), serverProperties.getError());
 }

 @Override
 public ResponseEntity error(HttpServletRequest request) {
 HttpStatus status = getStatus(request);
 if (status.equals(HttpStatus.INTERNAL_SERVER_ERROR)){
 return ResponseEntity.status(status).body(ResponseBean.SERVER_ERROR);
 }else if (status.equals(HttpStatus.BAD_REQUEST)){
 return ResponseEntity.status(status).body(ResponseBean.BAD_REQUEST);
 }
 return super.error(request);
 }
}
</code></pre>

The <code>ResponseBean</code> here is my custom pojo for response.

I am trying to set up a large-scale REST services server. We're using Spring Boot 1.2.1 Spring 4.1.5, and Java 8. Our controllers are implementing @RestController and the standard @RequestMapping annotations.

My problem is that Spring Boot sets up a default redirect for controller exceptions to <code>/error</code>. From the docs:

<blockquote>
 Spring Boot provides an /error mapping by default that handles all errors in a sensible way, and it is registered as a ‘global’ error page in the servlet container. 
</blockquote>

Coming from years writing REST applications with Node.js, this is, to me, anything but sensible. Any exception a service endpoint generates should return in the response. I can't understand why you'd send a redirect to what is most likely an Angular or JQuery SPA consumer which is only looking for an answer and can't or won't take any action on a redirect.

What I want to do is set up a global error handler that can take any exception - either purposefully thrown from a request mapping method or auto-generated by Spring (404 if no handler method is found for the request path signature), and return a standard formatted error response (400, 500, 503, 404) to the client without any MVC redirects. Specifically, we are going to take the error, log it to NoSQL with a UUID, then return to the client the right HTTP error code with the UUID of the log entry in the JSON body.

The docs have been vague on how to do this. It seems to me that you have to either create your own <a href="http://docs.spring.io/spring-boot/docs/1.2.2.RELEASE/api/org/springframework/boot/autoconfigure/web/ErrorController.html" rel="noreferrer">ErrorController</a> implementation or use <a href="http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/web/bind/annotation/ControllerAdvice.html" rel="noreferrer">ControllerAdvice</a> in some fashion, but all the examples I've seen still include forwarding the response to some kind of error mapping, which doesn't help. Other examples suggest that you'd have to list every Exception type you want to handle instead of just listing "Throwable" and getting everything.

Can anyone tell me what I missed, or point me in the right direction on how to do this without suggesting up the chain that Node.js would be easier to deal with?

Spring Boot REST service exception handling

Spring Framework

Spring Boot

服务器

容器

NoSQL

JSON

Java

我正在尝试设置一个大规模的REST服务服务器。我们使用的是Spring Boot 1.2.1、Spring 4.1.5和Java 8。我们的控制器实现了@RestController和标准的@RequestMapping注释。我的问题是Spring Boot为/error的控制器异常设置了一个缺省重定向。从文档中：se...

问Spring Boot REST服务异常处理
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Spring Boot REST服务异常处理EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Spring Boot REST服务异常处理
EN