My understanding is that since JAX-WS artifacts are portable, we don't need our own wsimport/wsgen variants unless we can make a point that we need to provide some added value.
Andreas On Mon, Jun 13, 2011 at 17:11, Sagara Gunathunga <[email protected]> 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. > > > Thanks ! > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://people.apache.org/~sagara/ > LinkedIn - http://www.linkedin.com/in/ssagara > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
