SAAJ 1.1 Not Always Supported

You might encounter a message telling you that a class in your implementation of JCS-SaaS Extension with Weblogic Server 10.3.6 does not support SAAJ 1.1.

If you are running JCS-SaaS Extension with Weblogic Server 10.3.6 and a JAX-WS custom business service and you call the external Web Service on the server, you might get this exception:

Call to Web Service failed, error: java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1

This occurs because of an issue with WebLogic’s default SAAJ implementation in package weblogic.webservice.core.soap. To correct this, from the command line interface, change the SAAJ implementation by setting the -name (-n) parameter of the set-system-property command to javax.xml.soap.MessageFactory and the -value parameter to weblogic.xml.saaj.MessageFactoryImpl:

./javacloud set-system-property -user userName -identitydomain identityDomain -serviceinstance serviceInstance -name javax.xml.soap.MessageFactory -value weblogic.xml.saaj.MessageFactoryImpl

For more information on set-system-properties, navigate to the $SDK_HOME/doc/index.html file (where SDK_HOME is the directory containing your Oracle Java Cloud Service - SaaS Extension installation) and click CLI-Javacloud.jar. You can also access all of the SDK documentation via the "Welcome App". Also see Using the Command-Line Interface to Monitor Oracle Java Cloud Service - SaaS Extension.