I think I found another small bug in the WSDL. The binding for WSRPServiceSoapBinding does not have a binding for the getDescription operation in the WSRPPortType. This too was causing .NET's WSDL import tool to choke. I added the following to the binding to make it work for me:
<wsdl:operation name="getDescription">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="getDescriptionRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://schemas.oasis-open.org/wsrp" use="encoded"/>
</wsdl:input>
<wsdl:output name="getDescriptionResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://schemas.oasis-open.org/wsrp" use="encoded"/>
</wsdl:output>
</wsdl:operation>
Does that make sense to folks?
Sasha.
-----Original Message-----
From: Rich Thompson [mailto:]
Sent: Friday, August 30, 2002 10:19 AM
To: ;
Subject: [wsia] [wsrp-interfaces] Draft spec v0.5
The doc file has now grown to 11MB ....
(See attached file: Draft Spec v0.5.ZIP)
