On Thursday, June 16, 2011 6:32:16 PM Sagara Gunathunga wrote: > On Tue, Jun 14, 2011 at 12:19 AM, Daniel Kulp <[email protected]> wrote: ....... > > This is definitely a better question for the dev@cxf list instead of > > the ws list. You can post and follow through nabble if you don't > > want to subscribe: > > > > http://cxf.547215.n5.nabble.com/cxf-dev-f569328.html > > Thanks Dan ! > > Of course I will write to dev@cxf if I get specific questions. Since > this is a high level discussion I thought it's ok to keep this > discussion on dev@ws so that people from both CXF and Axis2 are here.
Well, the main problem is that I don't think anyone (other than myself) that has worked on the CXF tooling actually does hang around dev@ws. That said, I'm happy to answer any questions, doesn't really matter where they are. :-) ........... > > The java2wsdl stuff is MUCH MUCH more involved. If you want to look, > > it's in tools/javato/ws. However, it does bring in a very large chunk > > of CXF. The java2* stuff pretty much uses the runtime components to > > setup a semi internal endpoint to pull the wsdl from. This was done > > to make sure the runtime and tools are completely in sync together by > > making sure the the code to produce the wsdl from the code is really in > > just one place. I'm not sure it will be possible to pull in the > > java2wsdl stuff without pulling in most of the JAX-WS minimal runtime. > > I spent sometime with CXF code base it seems wsdlto tools required > number of CXF dependencies and specially JavaTo integration require > much effort than that. wsdlto stuff is much much simpler. It does pull in cxf-rt-core and cxf-api, but the classes that are used from those are limited and could possibly be moved around a bit to make it simpler. javato stuff is way way more involved. That said, I have to question whether it's really needed unless the goal is to claim jax-ws compliance. I confess not knowing enough about Axis2 in the area of Java first development, but doesn't it already have some sort of runtime capability for Java first development? Doesn't it generate a wsdl a runtime? Basically, the java2* tools in CXF really serve a few purposes: 1) Generate the wsdl at build time. However, very few people actually do this and generally just use the runtime generated wsdl. 2) Generate JAX-WS specific artifacts required to pass the TCK. This would include the wrapper beans and fault beans. However, CXF itself doesn't need these beans. Neither does the JAX-WS RI with 2.2.x, but it is required for the JAX-WS TCK compliance. Since CXF doesn't require these, no-one generally generates them unless they want to use the generated beans as a starting point for some customizations. Basically, with the modern versions of CXF and Metro, the wsgen/java2ws tools are really irrelevant except for TCK compliancy. I'm not sure if it really would be needed for Axis2. Dan > Still I didn't dig into much details about this > integration. BTW is there any possibility to refactor CXF JAX-WS tool > into common code base so that both project can reuse it. Just my > thoughts not sure about the feasibility of this idea. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
