Override Built in Exception Mappers

[kauanmocelin]

Hello, I'm trying to override java.lang.Throwable but without success, I tried with @priority but the default built-in mapper is always called.

Is there any way to override the built in exceptions, like the ones listed here, with my own custom implementation?

I also tried overriding Exception (which is not listed among the built-in mappers), but that didn't work either.

version: 3.20.1

[lwitkowski]

Hey @kauanmocelin, remember that according to JaxRS specs, the best matching exception, meaning - handling the exact type of exception defined for it, or closest inheritance-wise is called by the framework.

Your mapper for Throwable is as far away from any specific exception type you can imagine, even Exception is closer, thus - DefaultExceptionMapper from this extension will always have precedence over your ExceptionMapperBase<Throwable>.

What I can suggest is to created mappers for both Throwable (if you really have to) and for Exception (and possibly for Error) and make sure they have higher priority than Priorities.USER.

[kauanmocelin]

Thank you @lwitkowski, that's correct. My goal is to implement a general exception mapper to customize the response for any unhandled exceptions.

I initially tried the following implementation:

@Provider
@Priority(5100)
public class GenericExceptionMapper implements ExceptionMapper<Exception>

However, this approach didn't work. The mapper was only triggered after I changed the priority to @Priority(100).

I think I found the root cause. When I use the quarkus-resteasy-jackson dependency, everything works fine, but with the reactive REST quarkus-rest-jackson, this problem occurs.

Is it supposed to work with reactive REST?