you were right ! That was finally a "stupid" classloader issue : I have transfered the saaj jars to the application classloader (they were previously packaged in the webapp) and this works. I still does not understand why the app needs to see the saaj classes, but I suppose that some Spring class based in the ear is responsible for this. many thanks for your help. MJ
Jeff Yu-4 wrote: > > An easiest way to verify it is to put the "saaj-impl-1.3.jar" & > "saaj-api-1.3.jar" in the $Weblogic_Home/jdk_../jre/lib/endorsed (create > it if it doesn't exist before). and then restart it to see if it works. > This way is to make sure that saaj-impl-1.3.jar is in front of classpath. > > If it works, that means there are other saaj version in the classpath, > and weblogic not pick up the saaj-impl-1.3.jar. > > Thanks > Jeff > > -- View this message in context: http://www.nabble.com/webservice-client-does-not-work-on-weblogic-9.2-tp14597531p14612734.html Sent from the cxf-user mailing list archive at Nabble.com.
