I have used both, but for different purposes. CXF worked great to parse a WSDL and create Java POJOs to interact with, so CXF is pretty good for client-side WSDL services. I’m currently using Jersey for server-side implementation and I am impressed with the simplicity of getting up-and-running with RESTful services using Jersey. As Jersey … Read more
About Apache CXF: CXF supports several standards including SOAP, the WSI Basic Profile, WSDL, WS-Addressing, WS-Policy, WS-ReliableMessaging, WS-Security, WS-SecurityPolicy, and WS-SecureConversation. Apache CXF offers both contract-last (starting with Java) and Contract-first (starting with the WSDL) approaches. Apache CXF implements JAX-WS and JAX-RS. About Spring WS: Spring WS offers “only” contract-first, starting from an XSD Schema. … Read more
Try this: String output = response.getEntity(String.class); EDIT Thanks to @Martin Spamer to mention that it will work for Jersey 1.x jars only. For Jersey 2.x use String output = response.readEntity(String.class);
The JAX-WS implementation built into the JDK really is just the basic soap stuff. If you need any of the more complex WS-* things like WS-Security, WS-RM, WS-Policy, etc…, you need to use one of the alternatives like CXF or Metro or Axis2. It can also depend on what you are trying to integrate with. … Read more
Keep in mind, I’m completely biased (PMC Chair of CXF), but my thoughts: From a strictly “can the project do what I need it to do” perspective, both are pretty equivalent. There some “edge case” things that CXF can do that Axis 2 cannot and vice versa. But for 90% of the use cases, either … Read more
I finally figured out the right answer to this question today. <plugin> <groupId>org.apache.cxf</groupId> <artifactId>cxf-codegen-plugin</artifactId> <version>${cxf.version}</version> <executions> <execution> <id>generate-sources</id> <phase>generate-sources</phase> <configuration> <sourceRoot>${project.build.directory}/generated-sources/cxf</sourceRoot> <wsdlOptions> <wsdlOption> <wsdl>${project.basedir}/src/main/resources/wsdl/FooService.wsdl</wsdl> <wsdlLocation>classpath:wsdl/FooService.wsdl</wsdlLocation> </wsdlOption> </wsdlOptions> </configuration> <goals> <goal>wsdl2java</goal> </goals> </execution> </executions> </plugin> Notice that I have prefixed the value in wsdlLocation with classpath:. This tells the plugin that the wsdl will be on … Read more