That definitely works if I can get at the raw XML response from the server. Which is what I posted and you used for $xml.
However, I should have been a bit clearer in my initial post. The XML response I posted above was captured via a tcpdump. The problem I'm getting is that when I use SOAP::Lite and print the results via Dumper, I'm only seeing the value in the body. So it looks like SOAP::Lite may be stripping the header off before I can get access to it.
Using the same code as from the first post, this is the what I see from the dumper printout
$VAR1 = bless( {
'resultCount' => '152',
'options' => undef,
'query' => 'SELECT DISTINCT huge-ass sql statement',
'filter' => 'DeviceType=\'NAS\'',
'maxResults' => '5000',
'firstResultPos' => '0',
'contextId' => 'ContextId_1364302533581',
'contextType' => 'Export_Device',
'internalResultCount' => '0'
}, 'WSContext' );
So, I'm thinking there needs to be something changed in these two lines in order to read the header (Or else, I need to do this with some completely different method) - just not sure what
## MAKE THE CALL, PRINT THE RESULTS
my $client = SOAP::Lite ->service($WSDL);
my $result = $client->initExportDevice($filter);
-
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.