Here's how I recently responded to a similar question on the Axis2 list...
If you're not using WS-Security the two stacks each have some advantages
and disadvantages. The main difference on the client side is that CXF is
best used with the JAX-WS frontend, which means you need to have access
to the WSDL at runtime (since that's how JAX-WS handles configuration).
Axis2's JAX-WS support is limited, but it does provide direct
configuration in ADB code generated from WSDL which is in many ways
simpler than the JAX-WS approach. On the server side, with Axis2 you
deploy a web app (WAR) which acts as a host for as many services as you
want to run, and also provides some basic monitoring and control
functions; with CXF you build and deploy a separate web app for each
service.
The two perform about the same unless you're using WS-Security. If
you're using WS-Security CXF gives *much* better performance than Axis2.
The way you configure WS-Security in CXF is also cleaner than in Axis2,
which requires a hacked-up version of the WSDL with embedded security
configuration parameters (CXF just has separate files with the security
configuration parameters).
My IBM developerWorks series on Java Web Services
(http://www.ibm.com/developerworks/views/java/libraryview.jsp?search_by=java+web+services:)
has details on the configuration issues and performance.
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
srinivas thallapalli wrote:
Hi All,
Can anybody please explain, what are the CXF advantages and disadvantages
over Axis2.
Thanks
