Before, the CXFJAXRSFilter was not in the filter chain because there were no REST endpoints not being a REST application. So whatever piece of code loaded the static resource before must've been adding the default.htm on and loading successfully but now the CXFJAXRSFilter code base for loading static resources is called which doesn't add the defualt.htm. :)
This is why I was suggesting the CXFJAXRSFilter only processed known REST endpoints and passed everything else off down the chain, rather than handling things itself. This example of a different code base for loading static content is an example, instead of leaving existing code to work untouched. (This might not be so easy though, just an impression/thought I have). It's close but not quite the same. Now I'm in a position where it's on the next request for /webappA/path3/subpath/file.abc -> CustomServlet but of course, static resource returns null (expected) and JAXRSInInterceptor is being called again with 404. Not sure why it isn't calling CustomServlet maybe the 404 just happens first? Thanks again for your help... really close to the bottom now I think. :) -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
