Changes in CXF 2.4.x
The below is applicable for CXF versions 2.3.x and older. Starting in CXF 2.4.0, the extensions are loaded internally by CXF automatically and you do not need to import all the cxf-extension-*.xml file. You only need to import classpath:META-INF/cxf/cxf.xml.
You can embed CXF within an existing Spring application. Since all XML configuration files are Spring xml files, the two approaches should be equivalent.
CXF includes Spring configuration files which configure the various CXF modules. You will want to import these into your application. Here is an example that imports the core CXF components, the SOAP binding, and the servlet transport:
To include all the CXF modules you can use cxf-all or a wildcard expression:
The only module cxf-all won't include is the servlet transport. If you want to include the servlet transport you must specify it specifically. This is because it will tell CXF to no longer use the standalone HTTP transport which is specified in the "classpath:META-INF/cxf/cxf-extension-http-jetty.xml" xml file, and you may not always want to do this.
This mailing list thread provides more information on CXF Spring files that may need to be imported in your web.xml.