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,
Just a gamble here, but docs for the Mule-CXF transport seem to suggest
that CXF is picky on the SAAJ version it wants ([1], see With Mule
Standalone section.) You may need to override the SAAJ version that
WebLogic is using. How you do that is unfortunately quite JEE
server-dependent. You may
Hi
Please check the saaj version in classpath, CXF shipped saaj-impl-1.3.jar and
saaj-api-1.3.jar. It might be conflict with the weblogic one.
Or you can check out the http://cwiki.apache.org/CXF20DOC/appserverguide.html
to see how to integrate with Weblogic.
HTH
Jeff
mjmjmj wrote:
I
Hi Jeff
thanks for your response.
I have already checked that saaj-impl-1.3.jar and saaj-api-1.3.jar are
present in the war part of the ear i deployed. I have also added the
following lines in the weblogic-application.xml DD file of the ear :
prefer-application-packages
