Problem

Complex Web service parameters in the WSDL (Web Services Definition Language) generated by the IWS (Integrated Web Services) server may not match the parameters in the PCML (Program Call Markup Language). For example, a portion of the PCML from an ILE application looks like the following:

PCML:
<struct name="PARMS">
<data name="ONE" type="char" length="10" usage="inherit" />
<data name="TWO" type="char" length="10" usage="inherit" />
<data name="THREE" type="packed" length="10" precision="0" usage="inherit" />

In the resulting WSDL, the same structure looks like the following:

WSDL:
<xs:complexType name="PARMS">
<xs:sequence>
<xs:element minOccurs="0" name="_ONE" nillable="true" type="xs:string"/>
<xs:element minOccurs="0" name="_THREE" nillable="true" type="xs:decimal"/>
<xs:element minOccurs="0" name="_TWO" nillable="true" type="xs:string"/>


Resolution

This is working as designed. There is not a direct correlation between final generated WSDL/Java Beans and the initial ILE procedure. The Axis 2 engine uses a type of alphabetization algorithm for the parameters of complex objects. When it generates the Java Beans and resulting WSDL, the fields may appear to be out of order. The generated Java code representing the ILE Web service knows the order of the parameters expected by the ILE program/service program and will handle the parameters appropriately.