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"
<[EMAIL PROTECTED]
> To
"[email protected]"
06/13/2007 10:11 <[email protected]>
AM cc
Subject
Please respond to jaxws-api module
[EMAIL PROTECTED]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<<inline: graycol.gif>>
<<inline: pic30397.gif>>
<<inline: ecblank.gif>>
