As Alessio mentioned….. CXF isn't even in that stack trace you provided. You're not even ending up using CXF at all. If the intention is to be using CXF, that's the first issue you need to resolve.
That said, most likely you can remove the SAAJ impl and saaj-api jars we provide and use the container provided versions. When running in J2EE container, the container does provide those and thus, you don't need to add them to the war/ear. Dan On May 3, 2013, at 11:22 AM, kdesin <kartheekdesine...@gmail.com> wrote: > Thanks Alessio. None of the versions we can change now per the client > requirements but can you please tell if there is a way to instruct CXF to > use it's own saaj implementation (sun) and Jbossws to use it's own native > libraries? > > What you have detailed is correct,it is coming because the endorsed folder > jar was taking precedence before coming to the CXF specific saaj lib in the > cxfwar-specif lib.Is there a way to separate these out and let them work > parallely as the native-saaj is required for the JBOSS-WS hosted service > > > Saludos > Kartheek > > > > > ----- > Saludos > Kartheek > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Problems-with-CXF2-6-1-and-jbossws-native-saaj-jar-tp5727143p5727150.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
