WSDL musings

[Glen Daniels <gd...@macromedia.com>]

I'd like to get a more general WSDL generation mechanism going, which can
take into account different providers, and also changes to the description
caused by deployed Handlers.  It seems to me that the good way to do this is
to have an editWSDL(MessageContext) method on Handler, and then use the
exact same process to invoke handlers that we do when actually processing a
message.  That way, whatever dispatch mechanism you have in place (custom,
URLMapper, JWSHandler...) will work to decide on the service, and the "core"
WSDL will be generated by the provider.

Can I get people's opinions on this?  I want to do something to generalize
WSDL composition ASAP, so if I don't hear anything from other committers in
the next day or two, I'm going to move ahead with this idea and we'll see
where it goes.

I think it's a good plan; the only other way I might do it is by fleshing
out ServiceDescription a little bit more (i.e. adding space for headers,
bindings, etc) and having the handler chains create one of those, which
would then get turned into WSDL...

Glen Daniels
Macromedia
http://www.macromedia.com/
                                Building cool stuff for web developers