Thanks for the config tips. Regarding the optional openejb.classloader.forced-load=org.apache.cxf...what will that do?
Yes I see now we should have just used webprofile. -Dave On Sat, Jun 7, 2014 at 11:20 AM, Romain Manni-Bucau <[email protected]> wrote: > Hi > > edit conf/conf.d/cxf.properties and conf/conf.d/cxf-rs.properties to set > the property: > > disabled = true > > > you can also add in conf/system.properties: > openejb.classloader.forced-load=org.apache.cxf > > > Finally using tomee webprofile would allow you to not have cxf in the > container > > > > > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-06-07 15:13 GMT+02:00 David Hoffer <[email protected]>: > > > I'm trying to get my EAR to work correctly when deployed in TomEE. My > EAR > > contains several WARs that are CXF based webservices. These work fine as > > standalone WARs in Tomcat and in TomEE but when I deploy as EAR in TomEE > > I'm getting CXF marshaling errors. > > > > I see that TomEE has several CXF jars in it's lib folder so I'm wondering > > if those are conflicting with the CXF jars in my EAR. > > > > How do I manage this? I don't think I need/want any CXF support from the > > container as I already have the jars I need. Does TomEE support this? > Do > > I have to configure TomEE to use my jars/etc? > > > > -Dave > > >
