Setting Precedence of Multiple @ControllerAdvice @ExceptionHandlers
问题 I have multipler classes annotated with @ControllerAdvice , each with an @ExceptionHandler method in. One handles Exception with the intention that if no more specific handler is found, this should be used. Sadly Spring MVC appears to be always using the most generic case ( Exception ) rather than more specific ones ( IOException for example). Is this how one would expect Spring MVC to behave? I'm trying to emulate a pattern from Jersey, which assesses each ExceptionMapper (equivalent