WS-I Compliance Continued
Stefan elaborates a bit on his concerns. However, as I indicated, it isn't necessary to separate out the abstract and concrete aspects of the WSDL. You simply annotate the bits that conform. e.g.
Technorati Tags: webservices, interoperability, wsi
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl"This should work. YMMV.
xmlns:tns="http://example.org/myservice"
xmlns:soapbind="http://schemas.xmlsoap.org/wsdl/soap"
xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/"
targetNamespace="http://example.org/myservice">
<wsdl:portType name="MyPortType">
<wsdl:documentation>
<wsi:Claim
conformsTo="http://ws-i.org/profiles/basic/1.1" />
</wsdl:documentation>
...
</wsdl:portType>
<wsdl:binding name="MyBinding" portType="tns:MyPortType" >
...
</wsdl:binding>
<wsdl:service name="MyService" >
<wsdl:port name="MyPort" binding="tns:MyBinding" >
<wsdl:documentation>
<wsi:Claim
conformsTo="http://ws-i.org/Profiles/SimpleSoapBinding/1.0" />
</wsdl:documentation>
<soapbind:address
location="http://example.org/myservice/myport" />
</wsdl:port>
<wsdl:port name="MyPort" binding="tns:MyBinding" >
<soapbind:address
location="http://example.org/myservice/mynonConformantPort" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Technorati Tags: webservices, interoperability, wsi
1 Comments:
Thanks for your help, Chris; I thought it might be easier to continue in one place for a few iterations, so I'm using a comment here :-)
Didn't you write that if I want my WSDL to be SSBP (not only BP) compliant, ALL of my bindings have to be SSBP? That's the only reason I'm so stubborn about this separation.
By Stefan Tilkov, at January 15, 2005 4:29 AM
Post a Comment
<< Home