You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by John Kaputin <KA...@uk.ibm.com> on 2005/09/22 17:08:15 UTC
Separate XmlSchema API and implementation
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
Fwd: Separate XmlSchema API and implementation
Posted by Arthur Ryman <ar...@gmail.com>.
---------- Forwarded message ----------
From: Arthur Ryman <ar...@gmail.com>
Date: Sep 25, 2005 3:42 PM
Subject: Re: Separate XmlSchema API and implementation
To: general@ws.apache.org
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 <sa...@opensource.lk> 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 <KA...@uk.ibm.com> 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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org
Re: Separate XmlSchema API and implementation
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+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 <KA...@uk.ibm.com> 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
Re: Separate XmlSchema API and implementation
Posted by Davanum Srinivas <da...@gmail.com>.
Eventually sure...but we don't have folks working full time on this code yet.
-- dims
On 9/22/05, John Kaputin <KA...@uk.ibm.com> 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