Simon Fell > Its just code > June 2004
Hey, looks like Scott Hanselman is coming to the bay area, and bonus for me, its only one floor away!, looking forward to seeing what Scott has to say.
Burried in this MSDN doc on choice's for attachments is the statement that Microsoft don't plan on supporting Soap with Attachments, which is the basis for the WS-I Attachments profile. Oh well, don't expect the current nightmare around soap attachments (for which we largely have MS to thank for) to go away anytime soon.
Very interesting post to Full Disclosure and NTBugTraq about the state of the MS Web site and its over active use of client side scripting to do simple server side stuff.
Been reading up on WS-Eventing (and WS-Events) recently, however the potential IP issues with both specs (the spec doesn't give you any IP license, nor indicate what terms any IP license might be on) would make me nervous about implementing either of them. I tend to agree with Steve Vinoski's post that this is hurting more than helping. Until the GXA folks detail the IP stance for all these specs, how is anyone outside of the GXA clan (not just people building tools, but people building services too) supposed to make any forward progress ?, or perhaps with my cynical bastard hat on, I'd say that was the point.
Chris is looking for speakers for the next XML DevCon, I'm hoping I can get out to this one.
Ted Neward has a post about web service tools, and their magic wand approach of generating WSDL / services from class definitions (ala ,NET / Java ), and how that's evil etc. Then goes on to say that doc/literal is going to save us. Whilst I agree that doc/literal is generally better than rpc/encoded (assuming tools get around to supporting all of XSD, the current mismatch of partial XSD support is an interop nightmare for authoring service WSDLs) using doc/literal won't magically save you either, its just as easy in both .NET & Axis to build doc/lit services from class definitions as it is to build rpc/enc services. In fact Ted's .NET magic wand sample actually is a doc/literal service. Basically, as much as the tool vendors would like you to believe otherwise, 3 years on from the SOAP 1.1. spec, its still a tedious error prone job to build good web services.