Re: SOAP::Lite, custom headers or raw xml ?

You were almost spot on with the first attempt, you just have to pass the SOAP::Header to the method call and SOAP::Lite will Do The Right Thing, I'd also suggest setting autotype off on the soap client as that suppresses the typing on the elements which might confuse some toolkits:

use SOAP::Lite +trace;
 
$uri = 'urn:Foo';
$proxy = 'http://localhost/';
$username = 'username';
$password = 'password';
 
my $client = SOAP::Lite
        ->readable(1)
        ->uri($uri)
        ->proxy($proxy);
 
$client->autotype(0);
 
my $Username = SOAP::Header->name('Username' => $username);
my $Password = SOAP::Header->name('Password' => $password);
          
my $UsernameToken = SOAP::Header->name('UsernameToken')
            ->value(\SOAP::Header->value($Username, $Password));
my $security = SOAP::Header->name('Security')
            ->attr({'xmlns' => 'http://schemas.xmlsoap.org/ws/2002/xx/
+secext'})
            ->value(\$UsernameToken);
 
$elem1 = SOAP::Data->name('ELEM1' => "value1");
$elem2 = SOAP::Data->name('ELEM2' => "value2");
$response = $client->mymethod($elem1,$elem2, $security);
[download]

This produces (for me anyway, let's all wait for an Anonymous Monk to turn up saying I'm lying in a bit:)

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope
    soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Header>
    <Security xmlns="http://schemas.xmlsoap.org/ws/2002/xx/secext">
      <UsernameToken>
        <Username>username</Username>
 
        <Password>password</Password>
      </UsernameToken>
    </Security>
  </soap:Header>
 
  <soap:Body>
    <mymethod xmlns="urn:Foo">
      <ELEM1>value1</ELEM1>
 
      <ELEM2>value2</ELEM2>
    </mymethod>
  </soap:Body>
</soap:Envelope>
[download]

/J\

Comment on Re: SOAP::Lite, custom headers or raw xml ? Select or Download Code

Replies are listed 'Best First'.
Re^2: SOAP::Lite, custom headers or raw xml ? by golemwashere (Acolyte) on Aug 18, 2006 at 16:49 UTC
Thanks for the tip, It worked!!! I now get a very similar request in my trace as the one expected... the only problem is I get <soap:Envelope> <soap:Body> and <soap:Header> tags instead of <SOAP-ENV:Envelope> <SOAP-ENV:Body> , etc... all the rest in the requests seem the same but the web service cryies out: <?xml version='1.0' ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schema +s.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><SOAP-ENV:Fault><faultco +de>SOAP-ENV:Server</faultcode><faultstring>null</faultstring><detail> +<IBResponse type="error"><DefaultTitle>Integration Broker Response</D +efaultTitle><StatusCode>20</StatusCode><MessageSet>158</MessageSet><M +essageID>10403</MessageID><DefaultMessage>A request must supply eithe +r a RequestorNode or a DistinquishedName</DefaultMessage><MessagePara +meters><Parameter>RequestorNode or DistinquishedName</Parameter></Mes +sageParameters></IBResponse></detail></SOAP-ENV:Fault></SOAP-ENV:Body +></SOAP-ENV:Envelope> [download] I tried messing up with $client->namespace but without any success. Any extra help would be greatly appreciated, sorry for beeing that newbie !!! P.S . I owe you a pint	[reply] [d/l]
Re^3: SOAP::Lite, custom headers or raw xml ? by gellyfish (Monsignor) on Aug 18, 2006 at 18:15 UTC
The namespace prefix really shouldn't matter to a well behaved toolkit. `<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap. +org/soap/envelope/"> ...` [download] is effectively the same as `<soap:Envelope xmlns:soap="http://schemas.xmlsoap. +org/soap/envelope/"> ...` [download] or even `<BlahBlahWoofWoof:Envelope xmlns:BlahBlahWoofWoof="http://schemas.xmls +oap. +org/soap/envelope/"> ...` [download] . The prefix used can be thought of as being "preprocessed" to represent the URI associated with it by the `xmlns:prefix="URL"` attribute. Of course the server might be badly behaved. However from the fault text you are getting I think the problem actually is that your are missing something from the request. I would suggest either consulting the WSDL for the service or the documentation or asking the person who is responsible for it to see where you have to place the `RequestorNode` or `DistinguishedName` and what the content is supposed to be. /J\	[reply] [d/l] [select]
Re^4: SOAP::Lite, custom headers or raw xml ? by golemwashere (Acolyte) on Aug 21, 2006 at 09:27 UTC
Everything works now, thanks! It's nice to see a place with competent and helpful people like this. I was using the wrong SOAPaction, btw I used Oxygen WSDL Soap analyzer which is the only tool I found which supports https to debug soap requests. P.S. I just hate peoplesoft integration broker's soap error messages, they are simply misleading.	[reply]


Welcome to the Monastery
	PerlMonks