Axis vs Axis2 vs CXF vs Spring Webservices

Axis or the Axis1.x - Open source webservice framework, implementation of the SOAP server, APIs for generating client/server side code for webservices.
Also ref: http://srbtechlog.blogspot.com/2011/06/apache-axis-commands.html


Axis2 - the next level of Axis1.x
Favors stand alone webservice applications.
Supported Data Bindings:XMLBeans, JiBX, JaxMe and JaxBRI, ADB(Axis native Data Binding). 
JaxME and JaxBRI are still considered experimental in Axis2 1.2
Supports WS-Addressing, WS-RM, WS-Security, and WS-I BasicProfile.


CXF - Celtix + XFire
Emphasizes code-first/contract-last design
Spring friendly
Supported Data Bindings:JAXB and Aegis; support for XMLBeans, JiBX and Castor will come in CXF 2.1.
Supports WS-Addressing, WS-Policy, WS-RM, WS-Security, and WS-I BasicProfile.


Spring Web Services
Document driven
Contract-first/code-last SOAP Services
Loose coupling between contract and implementation
Supports JAXB 1 and 2, Castor, XMLBeans, JiBX, and XStream
Implements WS-Security, Integrates with Spring Security (Acegi)


Axis2 can be configured to work with Spring
Integration takes place when Spring supplies one of its pre-loaded beans to the Axis2 Message Receiver defined in the AAR services.xml. Axis2 typically uses reflection to instantiate the ServiceClass defined in the services.xml used by the Message Receiver. Alternatively, you can define a ServiceObjectSupplier that will supply the Object.
Ref: http://axis.apache.org/axis2/java/core/docs/spring.html