Chapter 38. Pojo-Based Route

By default, the Camel CXF component marshals incoming Web service requests into the POJO data form, where the In message body is encoded as a list of Java objects (one for each operation parameter). The POJO data format has advantages and disadvantages, as follows:

The code presented in this chapter is taken from the following demonstration:

cxf-webinars-jboss-fuse-6.3/customer-ws-camel-cxf-pojo

cxf-webinars-jboss-fuse-6.3/customer-ws-camel-cxf-pojo

For details of how to download and install the demonstration code, see Chapter 34, Demonstration Code for Camel/CXF

The Camel CXF component is an Apache CXF component that integrates Web services with routes. You can use it either to instantiate consumer endpoints (at the start of a route), which behave like Web service instances, or to instantiate producer endpoints (at any other points in the route), which behave like WS clients.

POJO data format is the default data format used by the Camel CXF component and it has the following characteristics:

To implement and build the demonstration POJO-based route, starting from scratch, you would perform the following steps:

Figure 38.1, “Sample POJO Route” shows an outline of the route that is used to process the operations of the CustomerService Web service using the POJO data format. After sorting the request messages by operation name, an operation-specific processor bean reads the incoming request parameters and then generates a response in the POJO data format.