Invoking a remote web service from Camel
Camel's CXF Component makes calling a web service easy by defaulting to using POJOs for the request and response objects, and storing all of the other SOAP details in exchange headers in case you need them.
With Camel's built-in data type conversion and bean parameter-binding capabilities, you can easily call out to your Java methods that expect the body of the SOAP message as either a parameter or as a return type. Camel will automatically handle the conversions between Java and XML. When calling a web service, additional details, such as which operation name to invoke, are set in the exchange separately from the body of the message.
This recipe will show you the basic structure for calling a web service from a Camel route.
Getting ready
This recipe assumes that you have a project with JAX-WS artifacts created as shown in the Generating the service stubs from a WSDL recipe. To use the generated API, you need to include a dependency to that...