Spring MVC:确定哪个控制器在@ExceptionHandler中抛出了异常

Question

我用Spring Boot和百里香SpringMVC。我有返回百里香模板名称的普通控制器和用< code>@RepsonseBody注释的REST控制器。

假设我有一个< code > EntityNotFoundException ，它是由控制器调用的某个代码抛出的。如果抛出，我想分别为REST控制器返回一个404状态代码和一个错误页面或错误消息。

我当前对普通控制器的设置：

@ResponseStatus(HttpStatus.NOT_FOUND)
public class ResourceNotFoundException extends RuntimeException {
    public ResourceNotFoundException(String message) {
      super(message);
    }
}

@Controller
public class FooController {

  @RequestMapping("/foo") public String foo() {
    try {
       ...
    } catch (EntityNotFoundException enfe) {
      throw new ResourceNotFoundException(enfe.getMessage());
    }
    return "foo";
  }
}

对于REST控制程序，我不会捕获异常并让全局异常处理程序拾取它：

@Controller
public class BarController {

  @RequestMapping("/bar")
  @ResponseBody
  public SomeDto bar() throws EntityNotFoundException {
    ...
    return someDto;
  }
}

@ControllerAdvice
public class ExceptionHandlerAdvice {

  @ExceptionHandler(EntityNotFoundException.class)
  public final ResponseEntity<Object> handleEntityNotFoundExceptionEntityNotFoundException enfe) {
    return new ResponseEntity<>(enfe.getMessage, HttpStatus.NOT_FOUND);
  }
}

我也不想在我的普通控制器中捕捉和重新抛出。全局处理程序应同时处理：

  @ExceptionHandler(EntityNotFoundException.class)
  public final Object handleEntityNotFoundException(EntityNotFoundException enfe) {
    if (/* is REST controller? */) {
      return new ResponseEntity<>(enfe.getMessage(), HttpStatus.NOT_FOUND);
    } else {
      Map<String, Object> model = ImmutableMap.of("message", enfe.getMessage());
      return new ModelAndView("error", model, HttpStatus.NOT_FOUND);
    }
  }

有没有办法确定异常的来源，即控制器是否用@ResponseBody矿石注释？

Answer 1

您可以将错误代码用作源原因/点，或为从ResourceNotFoundException扩展的不同异常源创建单独的异常。

对于错误代码，您使用一个异常并处理不同的代码，对于额外的异常，您应该创建exrta类。

public class ResourceNotFoundException extends RuntimeException {
    private Long sourceErrorCode;//if you use java8 use Optional

    public ResourceNotFoundException(String message) {
      super(message);
    }

    public ResourceNotFoundException(String message , Long sourceErrorCode) {
      super(message);
      this.sourceErrorCode = sourceErrorCode;
    }    
}

扔

 ......
catch (EntityNotFoundException enfe) {
  throw new ResourceNotFoundException(enfe.getMessage() , ERROR_SOURCE_CODE);
}

和处理程序

 @ExceptionHandler(EntityNotFoundException.class)
  private Set<Long> REST_CODES = ..add... {code1 , code2...}

  public final Object handleSlugNotFoundException(EntityNotFoundException enfe) {
    //if you use java 8 use Optional
    if (REST_CODES.contains(enfe.getErrorCode())/* is REST controller? */) {
      return new ResponseEntity<>(enfe.getMessage(), HttpStatus.NOT_FOUND);
    } else {
      Map<String, Object> model = ImmutableMap.of("message", enfe.getMessage());
      return new ModelAndView("error", model, HttpStatus.NOT_FOUND);
    }
  }

并为错误代码创建类持有者或枚举，以避免代码重复

Answer 2

我会对普通控制器和REST控制器使用单独的异常，而不是用特殊的返回代码或消息来变魔术。这样，您可以编写简单的有针对性的异常处理程序。

@ResponseStatus(HttpStatus.NOT_FOUND)
public class ResourceNotFoundException extends RuntimeException {
    public ResourceNotFoundException(String message) {
      super(message);
    }
}

@ResponseStatus(HttpStatus.NOT_FOUND)
public class RestResourceNotFoundException extends RuntimeException {
    public ResourceNotFoundException(String message) {
      super(message);
    }
}

Answer 3

我找到了解决办法。您可以将当前控制器方法作为< code>HandlerMethod参数注入。

  @ExceptionHandler(EntityNotFoundException.class)
  public final Object handleEntityNotFoundException(EntityNotFoundException enfe, HandlerMethod handlerMethod) {

    boolean isRestController = handlerMethod.hasMethodAnnotation(ResponseBody.class)
        || handlerMethod.getBeanType().isAnnotationPresent(ResponseBody.class)
        || handlerMethod.getBeanType().isAnnotationPresent(RestController.class);

    if (isRestController) {
      return new ResponseEntity<>(enfe.getMessage(), HttpStatus.NOT_FOUND);
    } else {
      Map<String, Object> model = ImmutableMap.of("message", enfe.getMessage());
      return new ModelAndView("error", model, HttpStatus.NOT_FOUND);
    }
  }