I've updated the isCXFResource check to follow the same behaviour as the JAX-RS application logic itself. If the application's getClasses() or getSingletons() return something then Application sub-class fully controls the resources/endpoints so the isCXFResource check returns true and sends all requests through the pre-existing CXF filter code route. If they both return empty, it does the previous checks to see if they are valid REST endpoints (picked up by CDI scanner) first. This aligns it with REST service logic I described previously.
I believe this should cover the scenarios. OpenAPI TCK passes with this fix. Will create a PR for it. :) Just CDI Embedded left to fix if nothing new. I will leave the full run of tests running overnight and see how it is in the morning. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
