Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Wednesday October 13, 2004
01:33 PM

SOAP::WSDL :(

[ #21324 ]

Our customer appears to have set things up correctly at their end. Regrettably, SOAP::Lite is a bit, er, confusing. It's retrieving everything correctly, but it's being coy and refusing to actually let me have the data. I think I'll buy it flowers.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If the SOAP method returns multiple items (e.g., returns a Vector) see a recent blog entry [cwinters.com] I wrote after running into this. It is possible to make SOAP::Lite behave, just takes a little work...
  • I agree that SOAP::Lite is quite opaque.  In my work, I usually skip the "handy" wrappers that SOAP::Lite offers and dig into the XML.  Here's a snippet like what I use in my unreleased SOAPClient package

    sub call
    {
      my ($uri, $proxy, $timeout, $method, $args, $want) = @_;
      my @args = map {SOAP::Data->name($_, $args->{$_})} keys %$args;
      my $som = SOAP::Lite
         ->uri($uri)
         ->proxy($proxy, timeout => $timeout)
         ->c