So keep in mind, Jersey is a full implementation of JAXRS/JaxWS, which TomEE includes a full implementation of the same in the server lib directory (CXF). You really should _not_ be providing an implementation, that defeats the purpose of a Container like TomEE. Typically you compile against a spec, and at runtime the implementation is provided for you. If I were you, I'd run the "other app" in a plain Tomcat container in it's own JVM.
On Wed, Sep 18, 2019 at 6:03 AM dkwakkel <[email protected]> wrote: > When deploying a jaxrs war (attached) with openejb.classloader.forced-load > = > javax.ws.rs > set in conf/system.properties war deployment goes fine but the test > endpoint http://localhost:8080/w/test returns a 404. When removing this > property it is working fine again (I need to add the property to have > another war which uses jersey working) > > How-To-Repeat: > # Deploy attached w.war > # set in conf/system.properties openejb.classloader.forced-load = > javax.ws.rs > # Open http://localhost:8080/w/test > Result: 404 response > Expected: A result ('OK') > > Is this a bug? > > w.war <http://tomee-openejb.979440.n4.nabble.com/file/t376095/w.war> > > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html > -- Jonathan | [email protected] Pessimists, see a jar as half empty. Optimists, in contrast, see it as half full. Engineers, of course, understand the glass is twice as big as it needs to be.
