You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2011/02/07 21:30:57 UTC
[jira] Resolved: (CXF-3307) SAAJ Issue with Weblogic 10.3.4 or
10.3.3
[ https://issues.apache.org/jira/browse/CXF-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-3307.
------------------------------
Resolution: Won't Fix
Fix Version/s: Invalid
There's really not much that can be done from *CXF* to deal with classloader issues in the various J2EE servers. In this case, there really are a couple options:
1) Use the pre-classpath to put our SAAJ impl in place
2) Remove our saaj-impl and saaj-api jars and just use the container provided versions. That should work fine.
> SAAJ Issue with Weblogic 10.3.4 or 10.3.3
> -----------------------------------------
>
> Key: CXF-3307
> URL: https://issues.apache.org/jira/browse/CXF-3307
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.2.9
> Environment: Any OS - Weblogic Application Server 10.3.3 0r .4
> Reporter: D Dub
> Fix For: Invalid
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> When calling CXF SOAP services getting the following error
> Caused by: java.lang.IllegalArgumentException: com.sun.xml.internal.messaging.saaj.soap.LocalStrings != com.sun.xml.messaging.saaj.soap.LocalStrings
> Have always had to add the following two properties to the start up of Weblogic
> EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl"
> export EXTRA_JAVA_PROPERTIES
> EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Djavax.xml.soap.SOAPConnectionFactory=com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory"
> export EXTRA_JAVA_PROPERTIES
> But with the latest version we get this new error. I know it is a difference between the SAAJ impl in the JDk versus the impl in CXF.
> Adding saaj-impl-1.3.2.jar to the PRE_CLASSPATH of Weblogic fixes the issue but is that right?
> Thanks
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira