olio
asked on
Change prefix within soap header
We are developing a .NET client with WCF to access a 3rd party web service.
The service disregards our request when in this format:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
</s:Envelope>
The service however only accepts the following:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
</soapenv:Envelope>
It seems the 3rd party service restricts the prefix to only accept 'soapenv' even though we know that it does not normally matter.
What would be the simplest way to approach this? We would like to avoid using a proxy or similar. Is there a way to influence the way WCF generates this? Is there a code change/addition we can do to add/replace the prefix?
Thanks
The service disregards our request when in this format:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
</s:Envelope>
The service however only accepts the following:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
</soapenv:Envelope>
It seems the 3rd party service restricts the prefix to only accept 'soapenv' even though we know that it does not normally matter.
What would be the simplest way to approach this? We would like to avoid using a proxy or similar. Is there a way to influence the way WCF generates this? Is there a code change/addition we can do to add/replace the prefix?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We had to redevlop the code and there was not other solution to it.
what binding are you using to access the webservice? is that webservice also WCF based?
see whether this helps you
http://efreedom.com/Question/1-2386306/Change-SOAP-Envelope-Schema-WCF
Thanks and regards,
Venki