This is actually where the eclipse STP project probably comes in. It
does have some support for the JAX-WS/JWS annotation things via the
CXF tooling. I'm not sure on the current state of it though.
Dan
On Jun 12, 2008, at 11:21 AM, Jarek Gawor wrote:
This is not a problem with Axis2. Axis2 supports everything that we
need for Java EE 5. The problem is that support for web services in
the current WTP is very Axis2 specific (e.g. generates Axis2 specific
deployment descriptors) and is not very JAX-WS aware (e.g. does not
rely on annotations to generate proper wsdl).
So, yes, we'll need to determine if and when WTP will provide support
for JAX-WS but we will also need to know if it will become more Java
EE 5 aware. That is, instead of generating proprietary deployment
descriptors it generate Java EE 5 deployment descriptors (web.xml,
webservices.xml) so that web services developed with WTP can be
deployed on any app server that supports Java EE 5. But maybe that's
something we will need to do.
Jarek
On Wed, Jun 11, 2008 at 9:56 PM, Tim McConnell
<[EMAIL PROTECTED]> wrote:
Hi, One of the more obvious deficiencies in the current GEP is the
lack of
support for the JAX-WS compliant Web Services. I hope that we can
rectify
this in the next major release. Unfortunately, WTP does support
Axis2 but
although Axis2 supports many of the WS-* standards, it does not
necessarily
support the Java standards (e.g., JSR-224). So it seems to me that
we have
these three considerations:
1. Determine if and when WTP will provide support for JAX-WS
2. If WTP will provide support for JAX-WS in the next release
(i.e., WTP
3.0) still assume some customization to support Geronimo (in the GEP)
3. If WTP will not provide support for JAX-WS in the next release
(i.e., WTP
3.0) extend the existing Web Service wizards in WTP to support both
JAX-WS
and Geronimo (in the GEP)
Am I missing anything obvious ??
--
Thanks,
Tim McConnell
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
