I have a pretty hot project that I have to complete linking a .NET client to
an Apache AXIS web service. AXIS is expecting the SOAP message as
soapenv:Envelope, but .NET creates soap:Envelope.
How do I change the default namespace in .NET to generate the expected
soapenv:Envelope style messages.
Thank you very much for your help,
Chris
The namespaces are the things that have to agree.
so
the fragment
<Fred:Envelope xmlns:Fred="http://schemas.xmlsoap.org/soap/envelope/">
<Fred:Body>
<Harumph:Message xmlns:Harumph="urn:thisIsMyNamespace"> Hello
</Harumph:Message>
</Fred:Body>
</Fred:Envelope>
is exactly equivalent to
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:Message xmlns:ns1="urn:thisIsMyNamespace"> Hello
</ns1:Message>
</soap:Body>
</soap:Envelope>
or
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<zzz:Message xmlns:zzz="urn:thisIsMyNamespace"> Hello
</zzz:Message>
</soapenv:Body>
</soapenv:Envelope>
If you are having an interop problem, the soap != soapenv is not the source
of it.
-Dino
"Chris Snider" <csn...@reg.net> wrote in message
news:eaL1H5m...@TK2MSFTNGP11.phx.gbl...
Thanks for the info.
However, when I manually build the soap message using the soapenv:
namespace, the web service recognizes the change. I don't know if the web
service developers are using a homegrown parser or not. If there is a way
to instruct my .NET client to generate the soap message using the different
namespace, I would really appreciate learning how to do so.
Thanks,
Chris
"Dino Chiesa [Microsoft]" <din...@online.microsoft.com> wrote in message
news:O#qzbyoSE...@TK2MSFTNGP10.phx.gbl...
"Chris Snider" <csn...@reg.net> wrote in message
news:%23iUVADp...@TK2MSFTNGP09.phx.gbl...
"Dino Chiesa [Microsoft]" <din...@online.microsoft.com> wrote in message
news:%23R1y54M...@TK2MSFTNGP10.phx.gbl...
-Dino
"Chris Snider" <csn...@skycompsystems.com> wrote in message
news:uBwW4bkT...@TK2MSFTNGP11.phx.gbl...