SOAP请求命名空间问题
我需要一些澄清来准确理解 SOAP 请求对 .Net 3.5 ASMX Web 服务的要求。这是一个示例请求:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dp="http://www.datapower.com/schemas/management">
<soapenv:Body>
<spml:addRequest requestID="string" executionMode="synchronous" xmlns:spml="spmlnamespace">
<spml:psoID ID="23099469" targetID="string" />
<spml:data>
<spml:attr name='groupId'>
<spml:value>111111</spml:value>
</spml:attr>
<spml:attr name='mdn'>
<spml:value>5555555555</spml:value>
</spml:attr>
<spml:attr name='serviceId'>
<spml:value>SDCAT1</spml:value>
</spml:attr>
</spml:data>
</spml:addRequest>
</soapenv:Body>
</soapenv:Envelope>
这是否意味着我的 asmx Web 服务方法应命名为“addRequest”?这是否也意味着该方法应该采用两个参数,第一个参数为“psoID”类型,第二个参数为 spml 命名空间中定义的“data”类型?
I require some clarification on understanding exactly what a SOAP request is asking for with respect to a .Net 3.5 ASMX web service. Here's a sample request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dp="http://www.datapower.com/schemas/management">
<soapenv:Body>
<spml:addRequest requestID="string" executionMode="synchronous" xmlns:spml="spmlnamespace">
<spml:psoID ID="23099469" targetID="string" />
<spml:data>
<spml:attr name='groupId'>
<spml:value>111111</spml:value>
</spml:attr>
<spml:attr name='mdn'>
<spml:value>5555555555</spml:value>
</spml:attr>
<spml:attr name='serviceId'>
<spml:value>SDCAT1</spml:value>
</spml:attr>
</spml:data>
</spml:addRequest>
</soapenv:Body>
</soapenv:Envelope>
Does this mean that my asmx web service method should be named "addRequest"? Does it also mean that this method should take two parameters, the first of type "psoID" and the second of type "data" as defined in the spml namespace?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
事实证明,我能够使用 wsdl.exe 工具生成代理类,方法是:1)用“include”语句替换“import”语句,2)将第一个和第二个 xsd 文件合并到一个文件/命名空间中。感谢大家的投入。
It turns out I was able to use the wsdl.exe tool to generate the proxy classes by 1) replacing the "import" statements with "include" statements and 2) combining the first and second xsd files into one file/namespace. Thanks for the input all.