tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kirys <kirys...@gmail.com>
Subject Re: WARNING: No operation matching request path on a full jax-rs app
Date Mon, 06 Jun 2016 10:09:44 GMT
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" <rmannibucau@gmail.com> wrote:

> 2016-06-06 11:00 GMT+02:00 Kirys <kirys@neoteroi.org>:
>
> > 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).
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message