---------- Forwarded message ---------- From: Arthur Ryman <[EMAIL PROTECTED]> Date: Sep 25, 2005 3:42 PM Subject: Re: Separate XmlSchema API and implementation To: [email protected]
In fact, there is an EMF XSD model that we use at in the Eclipse Web Tools project for our WSDL 1.1 validator. Let's not worry about this yet though. -- Arthur On 9/24/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > +1 .. and Woden'ers you're welcome to take the charge on this! :). > > Sanjiva. > > On Fri, 2005-09-23 at 10:31 -0700, Davanum Srinivas wrote: > > Eventually sure...but we don't have folks working full time on this code > > yet. > > > > -- dims > > > > On 9/22/05, John Kaputin <[EMAIL PROTECTED]> wrote: > > > Has there been any thought yet on creating an API for ws-commons > > > XmlSchema, > > > separate from the implementation (e.g. as interfaces in separate > > > packages). > > > This would allow some other project's API to expose XmlSchema as an API, > > > without being tied to the ws-commons implementation. > > > > > > This may not be an issue for most Apache WS projects, but Woden for > > > example > > > will define a WSDL 2.0 API and implementation separately to cater for > > > users > > > who may wish to re-implement bits themselves. For example, if we could > > > expose XML schema through the Woden API using a ws-commons XmlSchema API, > > > then when Eclipse uses Woden it may choose to provide its own EMF-based > > > implementation of XmlSchema. > > > > > > I'm not expecting someone else to do all the work, just getting your > > > feedback initially. > > > > > > John Kaputin > > > IBM > > > > > > > > > > > > -- > > Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
