Recommendations to others considering Apache CXF:
Make good use of interceptors to ensure a smooth code-level integration for users of your CXF-based API client; e.g. if you don't explicitly map HTTP error responses to Java exceptions, the autogenerated proxy client will simply throw generic WebApplicationExceptions, which the users will then need to specifically traverse in order to determine the actual service-level error. Review collected by and hosted on G2.com.
What problems is Apache CXF solving and how is that benefiting you?
We use Apache CXF as the core of the Java client library for our On-Premise Enterprise Integration Platform (https://www.g2crowd.com/products/ips-enterprise-integration-platform) which has a JAX-RS compatible REST API for all management operations. For 20 different API subinterfaces (controllers) the CXF client took only about 100 lines of code (all just code-level configurations), and has been working rock-solid ever since. Review collected by and hosted on G2.com.