Enterprise Integration Zone is brought to you in partnership with:

Arun is a curious programmer who has spent the last 9 years trying to create better and faster programs. When the sun goes down, he experiments with various technologies and programming languages. He blogs at http://rerun.me. Arun is a DZone MVB and is not an employee of DZone and has posted 26 posts at DZone. You can read more from them at their website. View Full User Profile

Building Camel-CXF REST Service in OSGi for Karaf - Multicasting and Aggregation

  • submit to reddit

Please check out my other post on building plain CXF services (without Camel) in OSGi on Karaf.

This is a basic tutorial on how to

  1. create a CXF REST service
  2. multicast (and parallelize) the incoming request using Camel
  3. source data from two different services
  4. aggregate the response and
  5. finally return the consolidated result as JSON to the the end user.

You could download the entire codebase from github.

What this application does, in simple terms

The result expected from this service is a hardcoded response which looks like

As you could see from the image, the top portion of the response is sourced from a service called NameEmailService and the second portion of the response is sourced from a service called AgePhoneService. The calls to enrich both the data are done concurrently and the consolidated result entity - ConsolidatedSearchResult is populated.

The Project structure looks like this :

There are two baby steps for Step 1.

Step 1.a - Create a CXF REST Service

As you might have guessed, there’s nothing complicated in this step. Just an interface and an implementation.


public interface RestService {
    public String sourceResultsFromTwoSources(@PathParam("queryString") String queryString);


public class RestServiceImpl implements RestService {
    private static Logger logger= LoggerFactory.getLogger(AgePhoneServiceImpl.class);
    private NameEmailService nameEmailService;
    private AgePhoneService agePhoneService;
    public RestServiceImpl(){
    //Do nothing. Camel intercepts and routes the requests
    public String sourceResultsFromTwoSources(String queryString) {
        return null;
    public NameEmailResult getNameEmailResult(String queryString){
        logger.info("Invoking getNameEmailResult from RestServiceImpl");
        return nameEmailService.getNameAndEmail(queryString);
    public AgePhoneResult getAgePhoneResult(String queryString){
        logger.info("Invoking getAgePhoneResult from RestServiceImpl");
        return agePhoneService.getAgePhoneResult(queryString);
    public NameEmailService getNameEmailService() {
        return nameEmailService;
    public AgePhoneService getAgePhoneService() {
        return agePhoneService;
    public void setNameEmailService(NameEmailService nameEmailService) {
        this.nameEmailService = nameEmailService;
    public void setAgePhoneService(AgePhoneService agePhoneService) {
        this.agePhoneService = agePhoneService;

Note that the method implementation sourceResultsFromTwoSources returns a null. The truth is that this method doesn’t even get called when making a REST call. Camel intercepts all requests to the URL and routes it to various endpoints (calls two methods - getNameEmailResult() and getAgePhoneResult(), in our case).

Step 1.b - Create the Service Implementation

Kiddish implementations of the NameEmailService and the AgePhoneService are below :

public class NameEmailServiceImpl implements NameEmailService {
    public NameEmailResult getNameAndEmail(String queryString){
        return new NameEmailResult("Arun", "arun@arunma.com");
public class AgePhoneServiceImpl implements AgePhoneService {
    public AgePhoneResult getAgePhoneResult(String queryString){
        return new AgePhoneResult(32, "111-222-333");

Step 2, 3, 4 & 5

Well, I lied when I said 2,3,4 and 5 were 4 steps. They are all done as a single step using Camel routing and its Enterprise Integration Pattern implementations.

public class RestToBeanRouter extends RouteBuilder {
    public void configure() throws Exception {
        from ("cxfrs://bean://rsServer")
                .aggregationStrategy(new ResultAggregator())
                .beanRef("restServiceImpl", "getNameEmailResult")
                .beanRef("restServiceImpl", "getAgePhoneResult")

Our Routing explained

Simply put, what our routerbuilder does is that it

1) from ("cxfrs://bean://rsServer") Intercepts all requests to a JAX-RS server endpoint defined in the rest-blueprint.xml as

     <cxf:rsServer id="rsServer" address="/karafcxfcamel"
                  loggingFeatureEnabled="true" />

2) The .multicast() forwards the original request untouched to

1. `getNameEmailResult`  &
2. `getAgePhoneResult` methods in `RestServiceImpl` 

3) The .parallelProcessing() places concurrent calls to the methods.

4) The .aggregationStrategy(new ResultAggregator()) specifies how the results from various multicasted sources should be, well, aggregated.

Our aggregator looks like :

public class ResultAggregator implements AggregationStrategy {
    public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
        ConsolidatedSearchResult consolidatedSearchResult=null;
        if (oldExchange==null){
            consolidatedSearchResult=new ConsolidatedSearchResult();
        NameEmailResult nameEmailResult=newExchange.getIn().getBody(NameEmailResult.class);
        AgePhoneResult agePhoneResult=newExchange.getIn().getBody(AgePhoneResult.class);
        if (nameEmailResult!=null){
        if (agePhoneResult!=null){
        return newExchange;

Our Aggregator explained

The aggregate method in our ResultAggregator is a little crude but does the job.

  1. The aggregate method gets called for all multicasted endpoints whenever they finish.

  2. So, the first time, the oldExchange will be null. We take that as an opportunity to construct the final consolidated result entity that we wanted to respond to the user.

  3. We check whether the newExchange that comes in is the result of a call to the NameEmailService or AgePhoneService and populate the consolidated entity accordingly.

  4. Finally, we return the consolidated entity - the returning does two jobs.

    1. The consolidated entity comes in as oldExchange for the next call to the aggregate method. (more like chaining - the last returned object from the entity is the one which comes in as the incoming exchange for the next call)

    2. Gets returned back to the user if it is the last call of aggregate (all multicast endpoints calls are complete).

Published at DZone with permission of Arun Manivannan, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)



Charl Victor replied on Thu, 2013/10/24 - 6:54am

Wow, gotta love it!

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.