Hey! Thanks for the info. I used to think that the issue was with the root context, but from what you are describing this may not be the case, which does make some sense for your case. I was getting a little confused on how you were having some kind of endpoint clash, but apparently the issue is that CXF just takes over everything.
Let me implement a few test cases and check if there is something that can be done. Cheers, Roberto > On 30 Jan 2019, at 23:25, j4fm <[email protected]> wrote: > > So I got time to look at this again. > > It seems to be pretty clear that if you take an existing non-REST based > webapp and add REST endpoints with CXF, the CXFJAXRSFilter will then only > allow REST resources and static resources to be served for that whole > webapp. Even without a "/*" servlet mapping it prevents the default servlet > because JAXRSInInterceptor throws a 404 (line 173) if the request path isn't > recognised as a REST resource. > > Do you know if there is a reason why CXF doesn't just pass on non-REST paths > to the next filter in the chain just like it does when the request is a > non-HttpServletRequest or when it thinks the path is for a static resource? > I would think the default servlet would produce a 404 just fine if the > request path really did not exist. > > > > -- > Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
