We're currently trying to build a WS client from the WSDL provided by a vendor. The client will then be used by a Java web app to do its things (as you do).
usually there is only Axis that you use, however now JAX-WS has come to the equation.
What I'd to know is whether there has been an analysis done comparing JAX-WS vs Axis2, going through each advantages and disadvantages. What I've got so far is JAX-WS requires 1.5 and access to the WSDL at runtime.
I've used both JAX-WS and Axis2. Both are very good. Axis2 lacks of documentation (as opposed to Axis1) and it can be a bit difficult to learn. JAX-WS is a standard. Mostly I use Axis2 because not all app servers support JAX-WS.
Hope it helps.
SCJP 5.0, SCWCD 1.4, SCBCD 1.3, SCDJWS 1.4
Joined: Jul 25, 2005
Thanks for the link.
I'm actually looking for features comparison between the two. Load won't be an issue for this project.
its is not the only ways axis and jax-ws to create the client against the available WSDL. You can also adopt other ways like xfire.
However there are not much information available about the Axis client creation but its very simple to do that.
Just install the Axis2 from Apache site. Open a common prompt cd to %AXIS_HOME%/bin and execute the below command.
The following command will generate the java cleint under folder src in same path.