On 06/06/2016 09:59, Romain Manni-Bucau wrote:
I suspect it is cause there was no exception from a service bean but just no matching so ExceptionMapper resolution is not triggered at all - which makes sense but it would have been an elegant way to solve it.
Understood, but is it right that a jax-rs application doesn't produce a 404 error when a request doesn't mach any defined path?
