Re^2: SOAP::Deserializer problem

Ok. This get's me a step forward. The output is now

got 'command' item 'message'
got 'command' subitem 1 '<<undefined>>'
got 'command' subsubitem 1:1 '<<undefined>>'
got 'command' subitem 2 '<<undefined>>'
[download]

Nonetheless I still don't have the name of the XML nodes. What I eventually need is the value of such nodes. How could I access them?? Axel.

Comment on Re^2: SOAP::Deserializer problem Download Code

Replies are listed 'Best First'.
Re^3: SOAP::Deserializer problem by radiantmatrix (Parson) on Jul 30, 2007 at 14:24 UTC
I'm not entirely familiar with SOAP::Deserializer; I've generally used XML::Simple family of parsers, and I've not had such problems with them. Sorry I can't be of more help than that. <–radiant.matrix–> Ramblings and references The Code that can be seen is not the true Code I haven't found a problem yet that can't be solved by a well-placed trebuchet	[reply]
Re^4: SOAP::Deserializer problem by axelrose (Scribe) on Jul 30, 2007 at 15:52 UTC
Thanks for your idea. I use SOAP::Deserializer only because it is a natural part of processing SOAP responses. Trying again with another deserializer like this: `my $soap = SOAP::Lite ->uri($uri)->proxy( $proxyUrl, timeout => 5 ) ->deserializer(XMLRPC::Lite->new());` [download] I end up with the error message from XMLRPC::Lite "A service address has not been specified either by using SOAP::Lite->proxy() or a service description)" although there is a proxy. I can watch the request and the response on the wire. So my last chance seems to be overloading deserialize() with a custom deserializer `my $soap = SOAP::Lite ->uri($uri)->proxy( $proxyUrl, timeout => 5 ) ->deserializer(Deserialize->new()); package Deserialize; use warnings; use strict; use SOAP::Lite; use vars qw(@ISA); @ISA = ('SOAP::Deserializer'); sub deserialize { return $_[1] } 1;` [download] Cheers, Axel.	[reply] [d/l] [select]