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());
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 deserializerCheers, Axel.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;
In reply to Re^4: SOAP::Deserializer problem
by axelrose
in thread SOAP::Deserializer problem
by axelrose
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |