All WSDL Choice Elements are Appearing in Web Service Input for External Service. (Doc ID 1400921.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Java CAPS - Version: 5.1.3 and later   [Release: 5.1 and later ]
Information in this document applies to any platform.

Symptoms

Using Java CAPS to invoke an external web service that has a WSDL with choice elements defined. The input generated by Java CAPS for the
web service contains all of the choice elements regardless of whether these elements are populated.

Take for example the following;

<xsd:choice>
<xsd:element name="message1" type="trib:Input1"/>
<xsd:element name="message2" type="trib:Input2"/>
<xsd:element name="message3" type="trib:Input3"/>
</xsd:choice>

When the data is mapped from say JMS or a file to the WSDL choice element for 'message1' only, the input generated by Java CAPS for the external web service has all of the elements populated whereas only message1 is expected.

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