THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
CXFConsumer works as the CXF server, so we create the CXF server with the CXFEndpoint which holds the cxf endpoint information such as SEI class, wsdl location, service name and endpoint name etc. You can configure the cxf endpoint according to this schema in spring.
Now we just leverage the CXF's invoker to override the default invoker by setting a CamelInvoker to the ServerFactoryBean.
CXFProducer
CXF Client is used to send out the incoming message from the CXFProducer and pass the response back.
To support the client which just sends the stream request , we write the CxfClient and CxfClientFactoryBean.
...
To get the best reuse of the CXF generic message layer, we use the CXF feature API to setup the interceptors for different types message handling.
...
Binding the conduit and destination with the context endpoint
As CXF transport API side, CXF transport API includes Conduit and Destination that we need to implement with Camel.
We use the the CamelTemplate to send out the message for a certain endpoint in the CamelConduit, and bind a consumer process for the CamelDestination.
When you specify the endpoint URI that start with camel in CamelConduit or CamelDestination the endpoint address, Camel transport will bind it to the endpoint which is in the CamelContext.
...