【问题标题】:Why fetching URL with ?wsdl suffix produces wsdl with no operation info?为什么获取带有 ?wsdl 后缀的 URL 会产生没有操作信息的 wsdl?
【发布时间】:2016-02-25 14:47:06
【问题描述】:

我有 WCF WS 作为控制台应用程序运行,当使用 Web 浏览器 http://localhost:7903/MyService/?wsdl 获取 wsdl 时缺少操作信息

这是为什么呢?下面获取的wsdl还有用吗?

<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/"xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:i0="http://www.mycompany.com/nis/MyService/wsdl/v1.0"xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsa10="http://www.w3.org/2005/08/addressing"xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" name="ptMyService" targetNamespace="http://tempuri.org/">
<wsdl:import namespace="http://www.mycompany.com/nis/MyService/wsdl/v1.0" location="http://0.0.0.0:7903/MyService/?wsdl=wsdl0"/>
<wsdl:types/>
<wsdl:binding name="BasicHttpBinding_IptMyService" type="i0:IptMyService">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http"/>
</wsdl:binding>
<wsdl:service name="ptMyService">
<wsdl:port name="BasicHttpBinding_IptMyService" binding="tns:BasicHttpBinding_IptMyService">
<soap:address location="http://0.0.0.0:7903/MyService/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

实际的 WSDL 如下所示:

<?xml version="1.0" encoding="UTF-8"?>
<definitions
  xmlns:cmp="http://www.mycompany.com/nis/MyService/v1.0"
  xmlns:msgs="http://www.mycompany.com/nis/MyServicemessages/v1.0"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:tns="http://www.mycompany.com/nis/MyService/wsdl/v1.0"
  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
  xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
  targetNamespace="http://www.mycompany.com/nis/MyService/wsdl/v1.0"
  name="MyServiceService"
  xmlns="http://schemas.xmlsoap.org/wsdl/">

  <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" />
  <types>
    <xsd:schema>
      <xsd:import schemaLocation="mycompany.nis.MyServicemessages.xsd" namespace="http://www.mycompany.com/nis/MyServicemessages/v1.0" />
      <xsd:import schemaLocation="mycompany.nis.MyService.xsd" namespace="http://www.mycompany.com/nis/MyService/v1.0" />
    </xsd:schema>
  </types>


  <message name="mMyService">
    <part name="parameters" element="msgs:components" />
  </message>
  <message name="mMyServiceResponse">
    <part name="parameters" element="msgs:syncresult" />
  </message>
  <message name="GetComponentRequest">
    <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" />
    <part name="parameters" element="msgs:GetComponent" />
  </message>
  <message name="GetComponentResponse">
    <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" />
    <part name="parameters" element="msgs:GetComponentResponse" />
  </message>
  <message name="RequestHeaderMessage">
    <part name="RequestHeaderPart" element="msgs:RequestHeader" />
  </message>
  <message name="ResponseHeaderMessage">
    <part name="ResponseHeaderPart" element="msgs:ResponseHeader" />
  </message>

  <portType name="ptMyService">
    <operation name="MyService">
      <input message="tns:mMyService" />
      <output message="tns:mMyServiceResponse" />
    </operation>
    <operation name="GetComponent">
      <wsdl:documentation xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" />
      <input message="tns:GetComponentRequest" />
      <output message="tns:GetComponentResponse" />
    </operation>
  </portType>

  <binding name="bMyService" type="tns:ptMyService">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    <operation name="MyService">
      <soap:operation soapAction="MyServiceAction" />
      <input>
        <soap:body use="literal" />
        <soap:header message="tns:RequestHeaderMessage" part="RequestHeaderPart" use="literal" />
      </input>
      <output>
        <soap:body use="literal" />
        <soap:header message="tns:ResponseHeaderMessage" part="ResponseHeaderPart" use="literal" />
      </output>
    </operation>
    <operation name="GetComponent">
      <soap:operation soapAction="GetComponent" />
      <input>
        <soap:body use="literal" />
        <soap:header message="tns:RequestHeaderMessage" part="RequestHeaderPart" use="literal" />
      </input>
      <output>
        <soap:body use="literal" />
        <soap:header message="tns:ResponseHeaderMessage" part="ResponseHeaderPart" use="literal" />
      </output>
    </operation>
  </binding>

  <service name="MyServiceService">
    <port name="MyServicePort" binding="tns:bMyService">
      <soap:address location="http://localhost:7903/MyService" />
    </port>
  </service>
</definitions>

【问题讨论】:

  • 是这个问题吗? stackoverflow.com/q/4214815
  • 谢谢!可能。我试试这个,让你知道。如果是这样,请写下答案并获得赏金奖励。
  • 是的。有用。你可以写答案,我会接受 +100 赏金。

标签: web-services wcf soap wsdl


【解决方案1】:

确保您的操作方法没有将ReplyAction 设置为“*”,因为生成 WSDL 元数据的 WsdlExporter 会忽略此类方法。

[OperationContract(ReplyAction="*")]
string SampleMethod(string msg);

根据MSDN:

在服务中指定星号指示 WCF 不要向消息添加回复操作,如果您直接针对消息进行编程,这很有用。

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2014-12-30
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多