Oozie excludes a lot of jersey already but suspect some dep can leak it (jersey-server is typically not needed normally). Check you dependency:tree, should be easy to cut these deps.
Side note: wonder how linked to jersey it is but it is an asf project so there should be no blocker to make it cxf friendly, we have all the nice guys to do that if needed. 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-08-14 11:23 GMT+02:00 WhiTeY <[email protected]>: > Dear mauro2java2011, > > thanks a lot for your answer. I'm aware of that but unfortunatly this does > not remove my class loading conflicts with jersey. > > Have a nice day! > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/TomEE-Plus-default-REST-servlet-tp4679724p4679729.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
