params ordering in soap messages

[Nicolas De Loof <ni...@capgemini.com>]

Hi all,

I get some troubles using axis :

My service is defined by a WSDL that defines input message with one "msisdn" param and output with 3 ones, including
"msisdn" (in-out) (see wsdl at bottom *)


The SOAP messages generated by axis do not conform to this WSDL as params ordering is'nt compliant : in-out param is set
first, until it is defined in wsdl as 2d element

SOAP message :

 <soapenv:Body>
  <ns1:QueryCVEntryResponse ...>
   <msisdn xsi:type="xsd:string">447813322341</msisdn>  // Should be 2d element !
   <result xsi:type="xsd:int">0</result>                // Should be 1st element !
   <status xsi:type="xsd:int">0</status>
  </ns1:QueryCVEntryResponse>
 </soapenv:Body>


Do you have some sugestions to make it work ?


(*) from WSDL :

<operation name="QueryCVEntry">
    <input message="CRTRoot:QueryEntry" />
    <output message = "CRTRoot:QueryEntryResponse" />
</operation>

<message name="QueryEntry">
    <part name="msisdn" type="xsd:string" />
</message>
<message name="QueryEntryResponse">
    <part name="result" type="xsd:int" />
    <part name="msisdn" type="xsd:string" />
    <part name="status" type="xsd:int" />
</message>


This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.