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

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\

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

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


Pathologically Eclectic Rubbish Lister
	PerlMonks