CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes.

AOP implementations and other frameworks that use bytecode modification may generate synthetic methods on the SEI that cannot be controlled or customized by the user (for example, AspecJ generates getters/setters for generated members, and these methods cannot be removed). These methods will show up as operations on the SEI, which is usually not the desired behaviour. We locally patched CXF to avoid this, please see the attached patch that worked for us.