wsdl。exe结果在“SOAP 1.1绑定未找到”
[英]wsdl.exe results in “SOAP 1.1 binding was not found”
I'm trying to implement an HTML Parsing web service as described in Chapter 23 of ASP.NET Unleashed (1st ed.) and this MSDN article. So far, so good! However, I do get an annoying warning when using wsdl.exe to generate the class:
我正在尝试实现一个HTML解析web服务，正如在ASP的第23章中所描述的那样。NET释放(1个ed)和这个MSDN文章。到目前为止还好!但是，在使用wsdl时，我确实得到了一个恼人的警告。exe生成类:
Microsoft (R) Web Services Description Language Utility [Microsoft (R) .NET Framework, Version 2.0.50727.3038] Copyright (C) Microsoft Corporation. All rights reserved. Warning: This web reference does not conform to WS-I Basic Profile v1.1. SOAP 1.1 binding was not found: WS-I's Basic Profile 1.1 consists of implementation guidelines that recommend how a set of core Web services specifications should be used together to develop interoperable Web services. For the 1.1 Profile, those specifications are SOAP 1.1, WSDL 1.1, UDDI 2.0, XML 1.0 and XML Schema. For more details on the WS-I Basic Profile v1.1, see the specification at http://www.ws-i.org/Profiles/BasicProfile-1.1.html.
I'd like to conform to the specification if possible. I looked at the recommended page and found a couple pages on w3.org, but didn't find a concrete example of what xml elements I need to include in order to conform.
如果可能的话，我想要符合规格。我查看了推荐的页面并在w3.org上找到了几页，但是没有找到一个具体的示例，说明我需要包含哪些xml元素以符合要求。
In lieu of posting my xml, I'll just say the wsdl roughly conforms to what is used in the MSDN article (except I fixed the invalid URL for the XMLSchema on w3.org by adding ".dtd").
除了发布我的xml，我只说wsdl大致符合MSDN文章中所使用的内容(除了我在w3.org上通过添加“.dtd”修复了XMLSchema的无效URL)。
Thanks!
谢谢!
1 个解决方案
#1
6
Wsdl.exe use by default SOAP as the protocol to implement and in consequence tries to check the conformance to the Basic Profile. Anyway, wsdl.exe handles this and continues with only a warning. If you check the MSDN article file, you will note that the binding is configure to use HttpGet protocol. So, if you want to suppress the warning, run
Wsdl。使用默认的SOAP作为实现的协议，并尝试检查与基本概要文件的一致性。总之,wsdl。exe处理这个问题，并且只继续警告。如果您检查MSDN文章文件，您将注意到绑定是配置为使用HttpGet协议的。所以，如果你想抑制警告，就跑吧。
wsdl.exe /protocol:HttpGet <url or path>
However, the resulting proxy class is the same with the previous one.
但是，生成的代理类与前一个类相同。
Side note: You don't have to fix any URL that defines a namespace, since it is not used as URL but as identifier. Although many namespaces look like URLs, they need not point to actual resources on the Web. The namespace http://www.w3.org/2001/XMLSchema is defined by W3C in XML Schema recommendation.
附注:您不需要修复任何定义名称空间的URL，因为它不是作为URL使用的，而是作为标识符。尽管许多名称空间看起来像url，但它们不需要指向Web上的实际资源。名称空间http://www.w3.org/2001/XMLSchema由W3C在XMLSchema推荐中定义。
注意！
本站翻译的文章，版权归属于本站，未经许可禁止转摘，转摘请注明本文地址：http://www.silva-art.net/blog/2008/10/30/39ee5a4f4d7c478c5384df37c852fd2d.html。