Simon Fell > Its just code
I just posted details on a new endpoint for the soapbuilders doc/literal interop testing.
System.Web.Services.Description.ServiceDescription mmmmmm tasty !
ideas about autogenerating WSDL or other IDLs from UserTalk scripts. Steve Ivy has ideas about autogenerating WSDL or other IDLs from UserTalk scripts, but I think the very concept of generating IDL from code is flawed; it leads to interfaces that expose unnecessary implementation details. Supposedly the way to go is to write the IDL first, then write your app. [Hack the Planet] Wooo Hooo, the voice of reason !
This sounds interesting : [Sam Ruby's Radio Weblog] I can't resist: in the bootstrapping of the open discussion of WSDL, it looks like the thin cable has reached the other side. Now let me annouce my intentions. That plan is to produce a busy developers guide to WSDL.
- path / SOAPAction
- Method Namespace
- I also made a comment about the lack of types, which i can't find right now.
Hype Alert : InfoWorld : W3C's chairman talks about the momentum of the Web services standards effort. What a glowing picture that paints. Pity its absolute bollocks !. SOAP 1.2 is running way late, SOAP 1.1 was submitted in May 2000, over 18 months ago. WSDL 1.1 was submitted in March 2001, 10 months ago, and the W3C appear to have done preciesly nothing with it.
Bob Cunnings has posted a detailed agenda for the WSDL Interop F2F.