The client system workaround is required if the client system is running JDK 1.6. This workaround involves the following tasks:
Adding the SAAJ 1.3 JAR files to the classpath if they are not already present
Setting four system properties in the Ant build file for the client program
Make sure that your classpath includes the following JAR files:
On Solaris OS:
/usr/share/lib/saaj-api.jar /usr/share/lib/saaj-impl.jar
On Linux and HP-UX systems:
/opt/sun/share/lib/saaj-api.jar /opt/sun/share/lib/saaj-impl.jar
For example, if your Ant targets for a Linux system include a setting like the following, your classpath is correct:
<path id="classpath"> <fileset dir="/opt/sun/share/lib"> <include name="*.jar"/> </fileset> ... </path>
Add the following <sysproperty> tags to the <java> targets in your build.xml files:
<sysproperty key="javax.xml.soap.MessageFactory" value="com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl"/> <sysproperty key="javax.xml.soap.MetaFactory" value="com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl"/> <sysproperty key="javax.xml.soap.SOAPConnectionFactory" value="com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnectionFactory"/> <sysproperty key="javax.xml.soap.SOAPFactory" value="com.sun.xml.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl"/>