Glen wrote: >> IMO, the Axis engine desperately needs a "service metadata" abstraction, which I've been making noises about for a long time.
I don't think this should be tightly bound to WSDL, though I do think we should clearly be able to read WSDL into a ServiceDescription (assuming that's what it gets called) and write a ServiceDescription out as WSDL. The reasoning here is : 1) the engine has a lot of uses for this data even in situations where actual WSDL isn't required. 2) the WSDL data structures aren't the most efficient way to deal with this stuff. 3) WSDL is likely going to change at some point in the next year or so as the ws-desc group works on it - I think we can do a good job with defining clean abstractions around what we want, and then map that to whichever version of WSDL we're using in the future (as well as WSDL 1.1 for backwards-compatibility). << Seems a good idea. I am still gearing up to start looking at ways of integrating Axis with Cocoon with the goal of turning pipelines into services that are accessible via SOAP. The concept of "service metadata" seems like the kind of thing we would need to be able to describe what a pipeline (collection of pipelines) in Cocoon is capable of doing without having to WSDL'ize them. Matthew -- Open Source Group sunShine - Lighting up e:Business ================================================================= Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn Tel:+49-5251-1581-30 [EMAIL PROTECTED] - http://www.s-und-n.de Weblogging at: http://www.need-a-cake.com =================================================================
