So I was thinking on this: 1. It would be ideal to be able to configure if MP endpoints/filters are enabled/disabled by default and then enabled/disabled per-context (i.e. opt-out vs opt-in behaviour). In TomEE MicroProfile edition, I expect it would be enabled by default. In Plus/Plume, I expect it would be disabled by default and enabled per-webapp.
2. With only 1. it would be a shame to not be able to make use of MP on existing webapps. I was thinking on possible options for resolving the CXF/JAX-RS issue and had some ideas. a. Not sure if possible, but if JAXRSInInterceptor could not raise a 404 exception and instead return to pass down the filter chain it could work. b. The CXFRSFilter could do the same endpoint checks that JAXRSInInterceptor does and avoid calling it in the first place for non-REST paths. c. CXFRSFilter could read an "exclude paths" filter configuration for contexts to consider as not REST. d. CXFRSFilter could check for an attribute set by a previous filter to indicate not to process as a REST resource. Not sure if you had something else in mind. Let me know if I should raise a ticket or can test something out. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
