What's the Camel Transport for CXF
In CXF you offer or consume a webservice by defining its address. The first part of the address specifies the protocol to use. For example address="http://localhost:9000" in an endpoint configuration means your service will be offered using the http protocol on port 9000 of localhost. When you integrate Camel Tranport into CXF you get a new transport "camel". So you can specify address="camel://direct:MyEndpointName" to bind the CXF service address to a camel direct endpoint.
Technically speaking Camel transport for CXF is a component which implements the CXF transport API with the Camel core library. This allows you to easily use Camel's routing engine and integration patterns support together with your CXF services.
Integrate Camel into CXF transport layer
To include the Camel Tranport into your CXF bus you use the CamelTransportFactory. You can do this in Java as well as in Spring.
Setting up the Camel Transport in Spring
You can use the following snippet in your applicationcontext if you want to configure anything special. If you only want to activate the camel transport you do not have to do anything in your application context. As soon as you include the camel-cxf-transport jar (or camel-cxf.jar if your camel version is less than 2.7.x) in your app, cxf will scan the jar and load a CamelTransportFactory for you.
Integrating the Camel Transport in a programmatic way
Camel transport provides a setContext method that you could use to set the Camel context into the transport factory. If you want this factory take effect, you need to register the factory into the CXF bus. Here is a full example for you.
Configure the destination and conduit with Spring
The elements used to configure an Camel transport endpoint are defined in the namespace
You can specify the camel context in the camel destination
The camel context id which you want inject into the camel destination
You configure a Camel transport client using the
camel:conduit element and its children. The
camel:conduit element takes a single attribute,
name, that specifies the WSDL port element that corresponds to the endpoint. The value for the
name attribute takes the form portQName
.camel-conduit. For example, the code below shows the
camel:conduit element that would be used to add configuration for an endpoint that was specified by the WSDL fragment
<port binding="widgetSOAPBinding" name="widgetSOAPPort"> if the endpoint's target namespace was
camel:conduit element has a number of child elements that specify configuration information. They are described below.
You can specify the camel context in the camel conduit
The camel context id which you want inject into the camel conduit
Configure the destination and conduit with Blueprint
From Camel 2.11.x, Camel Transport supports to be configured with Blueprint.
If you are using blueprint, you should use the the namespace
http://cxf.apache.org/transports/camel/blueprint and import the schema like the blow.
camel:destination only has one camelContextId attribute, they doesn't support to specify the camel context in the camel destination.
Example Using Camel as a load balancer for CXF
This example shows how to use the camel load balancing feature in CXF. You need to load the configuration file in CXF and publish the endpoints on the address "camel://direct:EndpointA" and "camel://direct:EndpointB"