Value Order (Deserialization)

[Jo...@HBOSplc.com]

Hello,

I've used the wsdl tool to generate the stubs for a c++ client but I've
found that the order of values in the XML response doesn't match the
order of the values being read by the deserializer. The order mismatch
seems to cause the getElement calls to fail. I've got the deserializer
to successfully read the response by changing the order the values are
read in the automatically generated stubs but I'm wondering...

Is the order of the values in the XML guaranteed to be consistent?
If not then, is there a problem with the autogenerated stubs in that
they should be able to handle differing orders.
If yes, why has the stub generator created a deserializer for a
different order.

I guess it is possible that the wsdl file has changed since the server
was written and the client stubs produced. This would explain an order
mismatch when I've used the tool but I still would like to know if the
value order in the XML is guaranteed for a given service and if not,
shouldn't the deserializer be able to cope with differing orders.

Any help appreciated,

John

-- 

------------------------------------------------------------------------------
HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority.
==============================================================================