You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Jarek Gawor <jg...@gmail.com> on 2007/06/13 17:11:17 UTC
jaxws-api module
Hi,
Currently, in Geronimo we are using Sun's JAX-WS API definitions and
we would like to replace it with Axis2's JAX-WS API definitions.
However, the jaxws-api module in Axis2 contains class definitions from
three different specs: JAX-WS, JSR 181 (JWS), and some from common
annotations spec. In order to prevent conflicts (with Geronimo
definitions of JWS and common annotation classes) we would like to
have a module that only contains the JAX-WS API definitions. So I
would like to propose splitting the jaxws-api module into 3 modules.
That is:
1) Move all javax/jws/* files from jaxws-api module to a new module
named 'jws-api'.
2) Move all javax/annotation/* files from jaxws-api module to a new
module named 'common-annotations' (or something like that).
3) Leave all javax/xml/* files in jaxws-api module as is.
Another alternative would be to remove the javax/jws/* and
javax/annotation/* files from jaxws-api module altogether and just
make Axis2 use the Geronimo equivalents.
What do people think?
Thanks,
Jarek
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: jaxws-api module
Posted by Jarek Gawor <jg...@gmail.com>.
FYI, I removed the javax.annotation.* classes from the jws-api module
and added dependencies on the geronimo-annotation-spec library. So the
jaxws-api and jws-api modules should now only contain classes relevant
to the given spec.
Jarek
On 6/15/07, Jarek Gawor <jg...@gmail.com> wrote:
> Ok. For now I created 'jws' module and moved javax.jws.* and
> javax.annotation.* classes there. Once I manage to publish the
> Geronimo common annotations module as maven1 module I will remove the
> javax.annotation.* classes from the 'jws' module.
>
> Jarek
>
> On 6/15/07, Davanum Srinivas <da...@gmail.com> wrote:
> > Either way sounds ok to me.
> >
> > thanks,
> > dims
> >
> > On 6/13/07, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
> > >
> > >
> > >
> > > Jarek,
> > >
> > > I don't have a strong opinion either way. I think both methods are fine.
> > >
> > > Having Axis2 use the Geronimo APIs for the JSR-250 (common annotations) would actually be better for that particular module, since that would provide the complete set. I believe we only have the subset required for JAX-WS right now.
> > >
> > > Thanks!
> > > -Nick
> > >
> > >
> > > "Jarek Gawor" <jg...@gmail.com>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > "Jarek Gawor" <jg...@gmail.com>
> > >
> > > 06/13/2007 10:11 AM
> > >
> > > Please respond to
> > > axis-dev@ws.apache.org
> > >
> > >
> > > To
> > > "axis-dev@ws.apache.org" <ax...@ws.apache.org>
> > >
> > >
> > > cc
> > >
> > >
> > >
> > > Subject
> > > jaxws-api module
> > >
> > >
> > > Hi,
> > >
> > > Currently, in Geronimo we are using Sun's JAX-WS API definitions and
> > > we would like to replace it with Axis2's JAX-WS API definitions.
> > > However, the jaxws-api module in Axis2 contains class definitions from
> > > three different specs: JAX-WS, JSR 181 (JWS), and some from common
> > > annotations spec. In order to prevent conflicts (with Geronimo
> > > definitions of JWS and common annotation classes) we would like to
> > > have a module that only contains the JAX-WS API definitions. So I
> > > would like to propose splitting the jaxws-api module into 3 modules.
> > > That is:
> > >
> > > 1) Move all javax/jws/* files from jaxws-api module to a new module
> > > named 'jws-api'.
> > > 2) Move all javax/annotation/* files from jaxws-api module to a new
> > > module named 'common-annotations' (or something like that).
> > > 3) Leave all javax/xml/* files in jaxws-api module as is.
> > >
> > > Another alternative would be to remove the javax/jws/* and
> > > javax/annotation/* files from jaxws-api module altogether and just
> > > make Axis2 use the Geronimo equivalents.
> > >
> > > What do people think?
> > >
> > > Thanks,
> > > Jarek
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> > --
> > Davanum Srinivas :: http://davanum.wordpress.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: jaxws-api module
Posted by Jarek Gawor <jg...@gmail.com>.
Ok. For now I created 'jws' module and moved javax.jws.* and
javax.annotation.* classes there. Once I manage to publish the
Geronimo common annotations module as maven1 module I will remove the
javax.annotation.* classes from the 'jws' module.
Jarek
On 6/15/07, Davanum Srinivas <da...@gmail.com> wrote:
> Either way sounds ok to me.
>
> thanks,
> dims
>
> On 6/13/07, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
> >
> >
> >
> > Jarek,
> >
> > I don't have a strong opinion either way. I think both methods are fine.
> >
> > Having Axis2 use the Geronimo APIs for the JSR-250 (common annotations) would actually be better for that particular module, since that would provide the complete set. I believe we only have the subset required for JAX-WS right now.
> >
> > Thanks!
> > -Nick
> >
> >
> > "Jarek Gawor" <jg...@gmail.com>
> >
> >
> >
> >
> >
> >
> >
> > "Jarek Gawor" <jg...@gmail.com>
> >
> > 06/13/2007 10:11 AM
> >
> > Please respond to
> > axis-dev@ws.apache.org
> >
> >
> > To
> > "axis-dev@ws.apache.org" <ax...@ws.apache.org>
> >
> >
> > cc
> >
> >
> >
> > Subject
> > jaxws-api module
> >
> >
> > Hi,
> >
> > Currently, in Geronimo we are using Sun's JAX-WS API definitions and
> > we would like to replace it with Axis2's JAX-WS API definitions.
> > However, the jaxws-api module in Axis2 contains class definitions from
> > three different specs: JAX-WS, JSR 181 (JWS), and some from common
> > annotations spec. In order to prevent conflicts (with Geronimo
> > definitions of JWS and common annotation classes) we would like to
> > have a module that only contains the JAX-WS API definitions. So I
> > would like to propose splitting the jaxws-api module into 3 modules.
> > That is:
> >
> > 1) Move all javax/jws/* files from jaxws-api module to a new module
> > named 'jws-api'.
> > 2) Move all javax/annotation/* files from jaxws-api module to a new
> > module named 'common-annotations' (or something like that).
> > 3) Leave all javax/xml/* files in jaxws-api module as is.
> >
> > Another alternative would be to remove the javax/jws/* and
> > javax/annotation/* files from jaxws-api module altogether and just
> > make Axis2 use the Geronimo equivalents.
> >
> > What do people think?
> >
> > Thanks,
> > Jarek
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
> >
> >
> >
> >
>
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: jaxws-api module
Posted by Davanum Srinivas <da...@gmail.com>.
Either way sounds ok to me.
thanks,
dims
On 6/13/07, Nicholas L Gallardo <nl...@us.ibm.com> wrote:
>
>
>
> Jarek,
>
> I don't have a strong opinion either way. I think both methods are fine.
>
> Having Axis2 use the Geronimo APIs for the JSR-250 (common annotations) would actually be better for that particular module, since that would provide the complete set. I believe we only have the subset required for JAX-WS right now.
>
> Thanks!
> -Nick
>
>
> "Jarek Gawor" <jg...@gmail.com>
>
>
>
>
>
>
>
> "Jarek Gawor" <jg...@gmail.com>
>
> 06/13/2007 10:11 AM
>
> Please respond to
> axis-dev@ws.apache.org
>
>
> To
> "axis-dev@ws.apache.org" <ax...@ws.apache.org>
>
>
> cc
>
>
>
> Subject
> jaxws-api module
>
>
> Hi,
>
> Currently, in Geronimo we are using Sun's JAX-WS API definitions and
> we would like to replace it with Axis2's JAX-WS API definitions.
> However, the jaxws-api module in Axis2 contains class definitions from
> three different specs: JAX-WS, JSR 181 (JWS), and some from common
> annotations spec. In order to prevent conflicts (with Geronimo
> definitions of JWS and common annotation classes) we would like to
> have a module that only contains the JAX-WS API definitions. So I
> would like to propose splitting the jaxws-api module into 3 modules.
> That is:
>
> 1) Move all javax/jws/* files from jaxws-api module to a new module
> named 'jws-api'.
> 2) Move all javax/annotation/* files from jaxws-api module to a new
> module named 'common-annotations' (or something like that).
> 3) Leave all javax/xml/* files in jaxws-api module as is.
>
> Another alternative would be to remove the javax/jws/* and
> javax/annotation/* files from jaxws-api module altogether and just
> make Axis2 use the Geronimo equivalents.
>
> What do people think?
>
> Thanks,
> Jarek
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
>
>
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: jaxws-api module
Posted by Nicholas L Gallardo <nl...@us.ibm.com>.
Jarek,
I don't have a strong opinion either way. I think both methods are fine.
Having Axis2 use the Geronimo APIs for the JSR-250 (common annotations)
would actually be better for that particular module, since that would
provide the complete set. I believe we only have the subset required for
JAX-WS right now.
Thanks!
-Nick
"Jarek Gawor"
<jgawor@gmail.com
> To
"axis-dev@ws.apache.org"
06/13/2007 10:11 <ax...@ws.apache.org>
AM cc
Subject
Please respond to jaxws-api module
axis-dev@ws.apach
e.org
Hi,
Currently, in Geronimo we are using Sun's JAX-WS API definitions and
we would like to replace it with Axis2's JAX-WS API definitions.
However, the jaxws-api module in Axis2 contains class definitions from
three different specs: JAX-WS, JSR 181 (JWS), and some from common
annotations spec. In order to prevent conflicts (with Geronimo
definitions of JWS and common annotation classes) we would like to
have a module that only contains the JAX-WS API definitions. So I
would like to propose splitting the jaxws-api module into 3 modules.
That is:
1) Move all javax/jws/* files from jaxws-api module to a new module
named 'jws-api'.
2) Move all javax/annotation/* files from jaxws-api module to a new
module named 'common-annotations' (or something like that).
3) Leave all javax/xml/* files in jaxws-api module as is.
Another alternative would be to remove the javax/jws/* and
javax/annotation/* files from jaxws-api module altogether and just
make Axis2 use the Geronimo equivalents.
What do people think?
Thanks,
Jarek
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org