Hi, following the instructions given on http://cxf.apache.org/docs/application-server-specific-configuration-guide.html#ApplicationServerSpecificConfigurationGuide-Websphere (section "Add your own class loader") it is quite easy to get CXF up and running with WebSphere 6.1.
I verified the instructions with WebSphere 6.1.0.19 and 6.1.0.27. Maybe you can add these two versions to the above mentioned documentation. However, things are getting way more complicated if the Web Services Feature Pack for WebSphere is installed. With this feature pack installed, it is impossible to deploy an application using CXF, because the WebSphere Web Services engine (something based on Axis2: com.ibm.ws.websvcs.deployment.WASAxis2MetaDataProcessor.processWARMetadata) starts parsing the JAX-WS annotations of the services and tries to deploy the services. Up to fixpack 27 (6.1.0.27) there was no possibility to disable the WebSphere Web Services engine. Two months ago, IBM reacted to the problem and released the following fix: PK96989: ENABLE USE OF THIRD PARTY JAX-WS WEB SERVICES ENGINE IN WEBSPHERE This fix requires at least fixpack 27 (6.1.0.27). It allows to disable the WebSphere Web Services engine for the whole JVM by setting the JVM property com.ibm.websphere.webservices.DisableIBMJAXWSEngine=true or to disable the engine just for a specific module by adding DisableIBMJAXWSEngine: true to WAR/META-INF/MANIFEST.MF. According to IBM, this fix shall be included into fixpack 29. For details, please see http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK96989 Hope that this information may be helpful for some of you. Kind Regards, Martin
