My Oracle Support Banner

For RPC WSDLs JDeveloper Displays the WSDL Message Parts Out Of Order For Variables (Doc ID 1274133.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle SOA Suite - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Symptoms

Opening a RPC type of WSDL you note the order of the element definitions for message names.

In the JDeveloper project you open the .bpel file and in the "Structure" pane expand the Variables Variables-> Process -> Variables -> the variable associated with the RPC WSDL.

Notice that the order of elements is not the same as the ones defined in the WSDL.  The out-of-order appearance is purely cosmetic and has no impact on functionality.

For example the WSDL file orders the message as follows:

<wsdl:message name="getRequest">
<wsdl:part name='Code' type='xsd:string'/>
<wsdl:part name='local' type='xsd:string'/>
<wsdl:part name='town' type='xsd:string'/>
<wsdl:part name='service' type='xsd:string'/>
<wsdl:part name='accessLine' type='xsd:string'/>
<wsdl:part name='circutID' type='xsd:string'/>
<wsdl:part name='channel' type='xsd:string'/>
<wsdl:part name='destination' type='xsd:string'/>
<wsdl:part name='e2EData' type='xsd:string'/>
<wsdl:part name='pck' type='xsd:string'/>
<wsdl:part name='callerId' type='xsd:string'/>
<wsdl:part name='besUserId' type='xsd:string'/>
</wsdl:message>


Viewing the associated variable in the "Structure" pane shows the following order, which does not match the WSDL order:

callerId
CircuitId
service
Code
local
e2EData
accessLine
besUserId
channel
pck
town
destination




Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.