I'm trying to build a SOAP encoded message to send through a web service as part of a smoke-test to confirm that a web-services layer is functioning properly (It's part of a much larger application, but if this service is broken, we need to know like...yesterday).
I've got just about zero SOAP experience, so working with SOAP::Lite is a bit hazy for me but I've got this to generate the first in a sequence of SOAP encoded messages:
use strict;
use SOAP::Lite;
use HTTP::Cookies;
my $soap = new SOAP::Lite
->proxy( 'http://host.domain.com:80',
cookie_jar => HTTP::Cookies->new( ignore_discard => 1 ) )
->readable(1)
;
my $data =
SOAP::Data->name( 'login' => [
SOAP::Data->name('user_name' => 'uname')->attr({ xmlns => ''}),
SOAP::Data->name('password' => 'upass')->attr({ xmlns => ''}),
],
)->attr({ xmlns => 'data.someservice.somedomain' });
my $env = SOAP::Serializer->envelope( freeform => $data );
print $env, "\n";
My impression from the Looooooong abundant SOAP::Lite docs was that passing a true value to readable would yield formatted XML for... readability. Does this only apply to non-freeform envelopes?
dsb
This @ISA my( $cool ) %SIG
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|