Hi,
I am also very interested in improving GEP to support spec compliant web
services deployment.
Currently, the WTP Web Services Wizard packs a lot of jar files with every
web service deployed and this burdens project with a lot of generated files.
As Geronimo has inbuilt axis2 container
I just want to point out that if the generated stuff is properly
standards compliant, it should work fine for the CXF stack as well.
It would be good to make JAX-WS compliance the target for WTP so it
would be usable for both stacks.
Dan
On Jun 12, 2008, at 6:33 AM, Sainath
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
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
Hi,
It is good to hear that you are interested in contributing to Geronimo.
In order to get access to submit new documents or code, you first need
to submit a CLA.
Here is a link to help you find them:
http://www.apache.org/licenses/#clas
I would suggest emailing rather than mail/fax if
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI, Axis2 does support JAXWS 2.1. thx.
- -- dims
Tim McConnell 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
