WLS 10.3: Incorrect Soap Messages Generated When Invoking A Web Service
Last updated on MAY 24, 2017
Applies to:
Oracle Weblogic Server - Version: 10.3 to 10.3Information in this document applies to any platform.
Symptoms
In WLS 10.3.0, web service client jar file was generated by using clientgen task as a JAX-RPC type.
When the program invokes the web service, information is set properly in Java classes defined in the WSDL. However, the SOAP request message sent to the web service was incorrectly constructed. The message contains invalid references to attributes where the data is duplicated.
The SOAP message contains unusual formatting, such as a href to "#i3" which is not defined anywhere in the SOAP envelop. This causes the following exception on the client:
Exception message: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [[Server CodecHandler] Failed to decode Failed to decode message] FaultActor [null] Detail [<detail>weblogic.wsee.codec.CodecException: Failed to decode message
com.bea.xml.XmlException: failed to deref i3
</detail>]; nested exception is:
weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: [Server CodecHandler] Failed to decode Failed to decode message
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms