geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <>
Subject Re: Axis2: Using CXF tooling instead of Sun tooling to generate WSDL
Date Fri, 15 Aug 2008 12:35:09 GMT
Hash: SHA1

I agree with Jarek. We don't have the equivalent of wsgen or wsimport in Axis2.

- -- dims

Jarek Gawor wrote:
> I'm pretty confident in CXF tooling but not so much about Axis2. Sure,
> we can re-assess Axis2 tooling first. Is this something you can take a
> look at?
> Thanks,
> Jarek
> On Thu, Aug 14, 2008 at 5:13 PM, Lin Sun <> wrote:
>> Hi,
>> Do we have a feel about how stable is the CXF wsdl generation code,
>> besides tck?   I remember way back we decided we could not use Axis2's
>> wsdl generation code as it didn't support annotation.   Should we also
>> look into where Axis2's wsdl generation code is now and assess if we
>> should use Axis2's or CXF's?
>> Lin
>> On Thu, Aug 14, 2008 at 4:45 PM, Jarek Gawor <> wrote:
>>> Hi,
>>> Right now, when using Axis2 as the JAX-WS provider, Geronimo will use
>>> Sun tooling (wsgen/wsimport) to generate the WSDL and other artifacts
>>> for the web service. That requires some Sun libraries to be
>>> distributed with Geronimo such as jaxws-rt.jar, jaxws-tools.jar, etc.
>>> I am wondering what people think if we switched Geronimo to use CXF
>>> tooling instead of Sun tooling (in Geronimo 2.2 only; assuming CXF
>>> tooling passes all the TCK tests (which it does AFAIK)).
>>> Jarek
Version: GnuPG v1.4.6 (GNU/Linux)


View raw message