To put it simply, these specifications are astoundingly bad. The comment period ended October 4, although looking at the comment list archive shows that comments were still being received, and processed, as recently as last week. According to W3C procedure, at this point the Director can send the documents back to the group, or he can allow them to move forward and ask for implementation information as the next step in becoming an official W3C Recommendation.
It is my feverent hope that not only will Tim Berners-Lee send the documents back to the working group, but that he'll attend their next face-to-face meeting and spank everyone involved. WSDL 2.0 is the worst example of architecture astronautics I have ever seen. While these documents might be useful to someone developing a WSDL tool, they are practically useless for a web services developer who wants to use WSDL to define their interface.
Yikes. Seems I have to go and read through this stuff, finally.
Now I can recall why a lot of people still think SOAP and Web services is just a modern form of DCOM.
Those were the days where we had this great project and implemented our own (quite limited, though) SOAP stack for Solaris and used the SOAP Toolkit 1.0 Technology Preview for coding the SOAP layer on Windows in C++ and COM. Ahhhh...
A lot of people have asked me recently when I am going to release-to-web the next version of DynWsLib. DynWsLib is a quite successful (see version 1.4) .NET library to call Web services dynamically at runtime without having a static proxy implementation.
Today I wrapped up things and we from thinktecture are pleased to provide the lib to you - here it is. Please read through the article provided at the link and be sure to read the licence included in the download. Any feedback is appreciated. Thanks.