The namespace prefix really shouldn't matter to a well behaved toolkit.
is effectively the same as<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap. +org/soap/envelope/"> ...
or even<soap:Envelope xmlns:soap="http://schemas.xmlsoap. +org/soap/envelope/"> ...
. 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.<BlahBlahWoofWoof:Envelope xmlns:BlahBlahWoofWoof="http://schemas.xmls +oap. +org/soap/envelope/"> ...
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\
In reply to Re^3: SOAP::Lite, custom headers or raw xml ?
by gellyfish
in thread SOAP::Lite, custom headers or raw xml ?
by golemwashere
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |