Hi it can be for ears.
Do you care sharing a maven project reproducing it? Would like to ensure I test against the same packaging - just remove the business logic to keep a single hello world endpoint please. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-06-20 5:50 GMT+02:00 rvinjamu <[email protected]>: > Looks like this is a class loading issue. I have a library with some Jersey > classes in EAR/lib and this is being picked up first and the classes in > this > are naturally not able to pick up classes in the other jar packaged in > EAR/WARmodule/web-inf/lib. Looks like TomEE is following a PARENT-FIRST > approach to class loading. I see some other posts on the same issue. What > is > the solution to force TomEE follow the regular J2EE model - of loading the > WEB-INF/lib jars first? > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Classloading-issues-integrating-Jersey-2-16-and-apache-tomee-plus-7-0-0-tp4678794p4678962.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
