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

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

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

Replies are listed 'Best First'.
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]