Good point, but it is just a little counterintuitive, actually there is no "processor" designed for it. I'll try the code you provided and also catch all function approach. On Jun 6, 2016 11:39 AM, "Romain Manni-Bucau" <[email protected]> wrote:
> 2016-06-06 11:00 GMT+02:00 Kirys <[email protected]>: > > > 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? > > > > It wouldn't be right but it does. If question is: is it right it doesn't > respect servlet config? I think so since it is not the same content which > is manipulated. > > That said you can open an issue on CXF to make it easier to configure (you > can quote this thread or me if it helps). >
