In your XML on the data types is declared to be 'SessionStruct'. There are a couple of default types that come with XML; string and integers to name two.
SOAP::Lite comes with its own default parser, and this parser attempts to take your XML file and make it into a Hash. The problem is that it reads the type from the XML document and then calls a module to decode the data type for that XML element. When you have custom types, it does not know what to do and blows up.
XML has some definition documents that help to identify and support these custom formats. The problem for SOAP::Lite is that it does not know how to read these definition documents. Java had alot more work put into it than Perl and so its SOAP utilities can read these definition documents and can handle stuff like this.
What I ended up do is using SOAP::Lite to get the document and don't attempt to deserialize the document. Instead I used XML::Twig to parse my XML.
Hope that helps
In reply to Re: SOAP::Lite:Java vs Perl
by Herkum
in thread SOAP::Lite:Java vs Perl
by mrguy123
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |