admin管理员组文章数量:1417434
I have an old WSDL with SOAP structure as below:
The above one works fine from .NET as it is accepting Request object.
A new endpoint was provided to me which is throwing error in .NET when trying to pass Request object. The SOAP of this endpoint looks like this:
Does 'urn' in the second endpoint makes a difference ? In the first endpoint it is 'proc'.
I have an old WSDL with SOAP structure as below:
The above one works fine from .NET as it is accepting Request object.
A new endpoint was provided to me which is throwing error in .NET when trying to pass Request object. The SOAP of this endpoint looks like this:
Does 'urn' in the second endpoint makes a difference ? In the first endpoint it is 'proc'.
Share Improve this question asked Jan 31 at 10:39 RKhRKh 14.2k52 gold badges159 silver badges279 bronze badges1 Answer
Reset to default 1The namespace prefix (e.g. urn: and prod:) are not important, per se, rather how they are defined elsewhere in the message payload.
For example, if both requests look like this:
<soapenv:Envelope xmlns:urn="http://your.namespace.here">
and
<soapenv:Envelope xmlns:proc="http://your.namespace.here">
Then they're structurally and functionally equivalent. Clients and producers can use whatever namespace prefixes they like. It's not uncommon for the client and producer (service implementation) to have different namespace prefixes, especially if they're different platforms (e.g. Java and .NET).
本文标签: cSOAP request issue and difference in envelopStack Overflow
版权声明:本文标题:c# - SOAP request issue and difference in envelop - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1745267377a2650684.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论