This is a shortcoming in the (current) implementation of SOAP::Lite. The problem is that the object, implemented as a hash reference, is just serialized as a hash reference. Thus, there is no concern for the order of the keys. But element-order is significant in XML (unless otherwise stated) when using XML Schema, which most web-services (especially Java- and .NET-based ones) use in their WSDL definitions.
At the present time, there is no quick, simple solution to this. You have to write your own serializer, and you have to plug it into SOAP::Lite. I wrote an article for O'Reilly that touches on this in the context of talking to .NET services, but it would apply here, as well. The article is Five Tips for .NET Programming in Perl.
--rjray
In reply to Re: Trouble Passing Objects using SOAP::Lite
by rjray
in thread Trouble Passing Objects using SOAP::Lite
by fogues
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |