On Tue, Jun 14, 2011 at 12:19 AM, Daniel Kulp <[email protected]> wrote: > On Monday, June 13, 2011 8:41:47 PM Sagara Gunathunga wrote: >> I'm planning to do some works on Axis2 code base to get JAX-WS support >> for WSDL2JAVA and JAVA2WSDL tools . Writing a own module for Axis2 is >> a not a wise thing , at least for this moment. Calling a some other >> tool set within Axis2 tools is a most feasible option right now. One >> approach is invoke JDK WSImport/WSGen internally , this should work >> well but possible downside is we don't have any control for >> modifications and bugs. Other option is invoke CXF tools internally , >> again we can gain same results also we can get fixes quickly even we >> can contribute in code level too. >> >> Personally I would love to use CXF tools but still I haven't >> investigate required dependencies and compatibly of this. Appreciate >> if CXF folks can give their opinion on this idea. > > 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. > > In anycase, if you checkout CXF, the "module" that would be starting point > would be the tools/wsdlto/frontend/jaxws for the wsdl2java stuff. That's > definitely the easier of the two tools to look at. A "mvn copy- > dependencies" in there yields: > > commons-collections-3.2.1.jar jaxb-xjc-2.1.13.jar > commons-lang-2.6.jar > cxf-api-2.5.0-SNAPSHOT.jar neethi-3.0.0.jar > cxf-common-utilities-2.5.0-SNAPSHOT.jar oro-2.0.8.jar > cxf-rt-core-2.5.0-SNAPSHOT.jar stax2-api-3.1.1.jar > cxf-tools-common-2.5.0-SNAPSHOT.jar velocity-1.6.4.jar > cxf-tools-validator-2.5.0-SNAPSHOT.jar woodstox-core-asl-4.1.1.jar > cxf-tools-wsdlto-core-2.5.0-SNAPSHOT.jar wsdl4j-1.6.2.jar > geronimo-javamail_1.4_spec-1.7.1.jar xml-resolver-1.2.jar > jaxb-impl-2.1.13.jar xmlschema-core-2.0.jar > > which is a bunch, but you probably already have a bunch of those and the cxf-* > stuff could be shaded together (and likely have a bunch of stuff excluded from > them). Some may be excluded to use the in-jdk stuff (woodstox, mail). > > > 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. 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. Thanks ! > > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > Talend - http://www.talend.com > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara
