I think this will be especially useful for implementing special purpose WSDL. For example, the following article shows how to return just the types or schema information.
Splitting up WSDL: The Importance of targetNamespace http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/html/service08202002.asp Another example is something that could be parsed by the Microsoft XSD utility. Good idea. Rick -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2003 1:16 PM To: [EMAIL PROTECTED] Subject: Re: ?wsdl and such Doug Davis wrote: > > > > > We have some mods to axis to allow people to plug-in their own > query string processor. This also moves the processing of ?wsdl, > ?list and ?method into these pluggable units. We use this in > the latest version of the ETTK to enable the use of > ?wsdldoc (think javadocs for wsdl). You add new plug-ins by > adding them as parameters to the "http" transport in the wsdd. > This also means people can more easily choose which query strings > to support. I was going to just commit the changes to axis but > I wanted to make sure there wasn't any objection to this > slight design change. > -Dug > +1. slick.
