拦截器和全局异常处理

时间:2021-04-12 10:36:10

标签: spring-boot exception interceptor

我有一个后拦截器。当控制层执行并返回信息时,将执行后拦截器。这时候,全局异常处理会捕捉到post-interceptor中的异常,并返回提示信息。使用“postman”来测试和控制层和全局异常处理的信息同时返回。这真的回来了吗?我写了一个测试示例。同样的情况,只返回控制层的信息。我认为它应该返回全局异常处理的信息。

控制器

@RestController
@RequestMapping("/v1/book")
@Validated
public class BookController {

    private final BookService bookService;

    public BookController(BookService bookService) {
        this.bookService = bookService;
    }

    @GetMapping("/search")
    public R searchBook(@RequestParam(value = "q", required = false, defaultValue = "") String q) {
        return R.select(bookService.getBookByKeyword(q));
    }
}

拦截器

public class LogInterceptor extends HandlerInterceptorAdapter {

    public LogInterceptor(LoggerResolver loggerResolver) {
        this.loggerResolver = loggerResolver;
    }

    @Override
    public void postHandle(HttpServletRequest request, HttpServletResponse response, Object handler, ModelAndView modelAndView) {
        // There will be a runtime exception here
    }
}

全局异常处理

@Order
@RestControllerAdvice
@Slf4j
public class RestExceptionHandler {

    /**
     * Exception
     */
    @ExceptionHandler({Exception.class})
    public R processException(Exception exception) {
        log.error("", exception);
        return R.error();
    }
}

结果

{
    "code": 200,
    "data": [
        // ...
    ],
    "type": "success",
    "message": "OK"
}{
    "code": 500,
    "type": "error",
    "message": "Internal Server Error"
}

"R extends HashMap",用于统一返回结构。

1 个答案:

答案 0 :(得分:0)

看着你的代码片段,我不确定 searchBook 和 processException 中的那些 R 是什么

试试这个(编辑 processException 以满足您的规格):

@GetMapping("/search")
public ResponseEntity<?> searchBook(@RequestParam(value = "q", required = false, defaultValue = "") String q) {
    return new ResponseEntity<>(bookService.getBookByKeyword(q), HttpStatus.OK);
}

@ExceptionHandler({Exception.class})
public ResponseEntity<?> processException(Exception exception) {
    return new ResponseEntity<>(new ErrorDTO(exception.getMessage()), HttpStatus.UNPROCESSABLE_ENTITY);
}