WSDL has always been one of the key components on which Web Services have been built. Although WSDL 1.1 never achieved the status of "standard" (it's only ever been a W3C Note, it quickly became a defacto standard. Some argue that this is simply because there is nothing better, whilst others believe WSDL 1.1 is perfect and needs no update. However, work on WSDL 2.0 has been going on for quite some time. WSDL 2.0 differs significantly from its predecessor, with amongst other changes:
- a new component model, intended to make it easier and more flexible to describe services and reuse them.
- a richer syntax for defining quality of service aspects of services, using features and properties or WS-Policy.
- a richer set of message exchange patterns.
- interface inheritance.
But it is true to say that it has added a lot of complexity over 1.1 and backwards compatibility is not something that has been a core requirement for the technical committee.
Although WSDL 2.0 has been around as drafts for a while, it is still not an official standard. That's where the Web Services Description Working Group comes in: their job is to agree on what that standard will look like and they were due to finish on the 31st of December 2006. However, they have recently applied for and received an extension to the 30th of June 2007, so a standard is unlikely before this new date. Apparently this is as a result of feedback and extra work required from the Nov ember implementers event and the Interoperability Dashboard.
How important is this delay to the take-up of WSDL 2.0? Is WSDL 2.0 right for the industry anyway? The WS-Addressing working group has had trouble getting enough implementations within the technical committee to ratify their own proposed work with WSDL 2.0. The community at large seems split over whether or not WSDL 2.0 is a good thing or a bad thing. Many critics cite the complexity of the specifications as a barrier to understanding, using and/or implementing WSDL 2.0; the fact that it introduces yet another data model; the lack of backwards compatibility (which means yet more new tool support is required); and perhaps that WSDL 2.0 may be a solution looking for a problem. However, supporters dispute the complexity argument; that WSDL 2.0 goes beyond "old style" Web Services to support HTTP/REST; that it offers better support for loose coupling; and that it supports improved interoperability
What do you think?
/filters:no_upscale()/sponsorship/topic/e235ba45-310a-4df5-a765-76f3b5463eb2/ScyllaDBLogoRSB-1680280572596.png)
/articles/cognitive-load-platform-engineering/en/smallimage/logo-1668609260559.jpg){kind=logo}
/presentations/infrastructure-control-plane/en/smallimage/Daniel Mangum-s-1665739290818.jpg)
/presentations/empathy-software-development/en/smallimage/qcon-plus-s-1680292453897.jpeg)
/presentations/operationalizing-ai/en/smallimage/qcon-plus-s-1680292123806.jpeg)
/articles/culture-trends-2023/en/smallimage/InfoQ-Trend-Report-logo-1680287660356.jpeg){kind=logo}
/articles/finops-systems-thinking-lens/en/smallimage/12-places-to-intervene-rethink-FinOps-using-a-systems-thinking-lens-small-1679995317220.jpg)
/articles/secure-software-development-gitops/en/smallimage/accelerating-secure-software-delivery-lifecycle-with-GitOps-small-1679658720410.jpg)
/presentations/refactoring-rust/en/smallimage/qcon-plus-s-1679694299933.jpeg)
/presentations/aws-apache-airflow/en/smallimage/qcon-plus-s-1679694143127.jpeg)
Community comments
Judging from the comments list...not really :)
by Jim Murphy,
Judging from the comments list...not really :)
by Jim Murphy,
Your message is awaiting moderation. Thank you for participating in the discussion.
I see a ton of WSDL of various sorts from all walks of life. Folks still using rpc-encoded, mostly the various doc-lits (wrapped and bare), even some fringe rpc-lit, add to that custom bindings for various stacks and custom protocols etc. etc. All tolled 100s of WSDLs. I've only ever seen 1 actual WSDL 2.0 document - from someone at Amazon - can't even remember the service. Natch, it made use of the REST binding.
Often times its difficult to get folks to think of WSDL at all. Clearly that's because the current tool crop makes code-first so much more compelling for a developer - and staying in a vendor's type system/world view is good for the vendor. That's the real issue though its hard to defend WSDL 1.1 but its what we have.
I think that unless and until the major stack vendors start supporting WSDL 2.0, it will be of dubious value. My impression is that you get to re-tool technology on this scale every decade or so and as far as web services is concerned the major pieces are in place. We have what we're going to use.
Jim Murphy
Mindreef, Inc.