title: Setting Precedence of Multiple @ControllerAdvice @ExceptionHandlers
body: <p>I have multiple classes annotated with <code>@ControllerAdvice</code>, each with an <code>@ExceptionHandler</code> method in.</p>
  <p>One handles <code>Exception</code> with the intention that if no more specific handler is found, this should be used.</p>
  <p>Sadly Spring MVC appears to be always using the most generic case (<code>Exception</code>) rather than more specific ones (<code>IOException</code> for example).</p>
  <p>Is this how one would expect Spring MVC to behave? I'm trying to emulate a pattern from Jersey, which assesses each <code>ExceptionMapper</code> (equivalent component) to determine how far the declared type that it handles is from the exception that has been thrown, and always uses the nearest ancestor.</p>