This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

WS-I Compliance Continued

Stefan Tilkov,

More from Chris regarding WS-I. I’ll have to elaborate a bit: In his first post, Chris wrote:

However, there is a twist to the use of extensibility points in WSDL bindings if you want to also claim conformance to the Simple Soap Binding Profile 1.0 as it constrains the WSDL binding to be only the WSDL SOAP binding, exclusive of any extensions.

My understanding of this restriction (which may well be wrong) led me to a workaround, which I’ll have to describe in more detail. My goal is (logically) depicted in the following diagram:

Ws-I-1

So what I’m intending to do is having a BP 1.1 compliant wsdl:portType with a) a BP 1.1 compliant and SSBP 1.0 compliant wsdl:binding and b) a binding to some proprietary (or at least non-compliant) transport. From Chris’s last post, I gather that I can’t claim conformance if not all of my bindings are compliant, so my idea would be to alleviate this with the following physical separation:

Ws-I-2-1

This way, the physical (right-most) WSDL file could be delivered to and used by WS-I BP and SSBP compliant services, while we would still be able to have additional bindings. Clients who do not understand this binding would never even see it. The only downside would be that (IIRC) I would have to use different service names in the different physical WSDLs.