MHonArc v2.5.2 --> wsia message [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home] Subject: RE: [wsia] [wsrp-interfaces] Draft spec v0.5
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsia] [wsrp-interfaces] Draft spec v0.5
Yup ... it was still called getServiceDescription() Sasha Aickin <AlexanderA@plumt To: wsia@lists.oasis-open.org, wsrp-interfaces@lists.oasis-open.org ree.com> cc: Subject: RE: [wsia] [wsrp-interfaces] Draft spec v0.5 09/03/2002 10:50 PM 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.
OASIS Open400 TradeCenter, Suite 5900Woburn, MA 01801USA
Phone+1 781 425 5073
Get Involved
Join an Open Project
Join a Technical Committee
About UsPrivacy