Skip to main content

Integration Project- Micro Services Migration Story with JBoss BPM Travel Agency - Part Three

Part Three - Retrieving Data with JDBC

In the post, I am going to show you how to create the fuse side travel agency demo from scratch. In the original Traveling Agency project, the hotel and flight information are all hardcoded in the application, in the Fuse version, I moved the settings to database. So in the project, you will find that there is a H2 database (File) installed. If you want to know more about the micro service architecture of the demo, please see this post for more details. We are going to concentrate on creating the promotion recommendation service of flights and hotel. Using the Camel JDBC components. I am using Hotel promotion service as example, the same applies to flight too, This service lists all the available hotels to the client with condition like the location of the hotels. After retrieving all the possible hotel data from database, it'll either randomly pick one of them, or create a default hotel.

First we need to collect the request from messaging broker, then using the input as parameters in our SQL statement, then query database using Camel-JDBC component, and process the list into Java object, then randomly choose on hotel from the list using a customize POJO bean. At last return the result back to broker.

There are two configuration you will need to predefine 2 configuration, 
1. Location and authentication of messaging broker


2. Datasource 

I love to turn data into POJO so it's easier to process in my java code, therefore I am going to create an object type "ResortInfo" to hold the data.
package org.blogdemo.travelagency.promotionhotel;

import java.math.BigDecimal;

public class ResortInfo implements Serializable{

  private static final long serialVersionUID =  
  int hotelId;
  String hotelName;
  BigDecimal ratePerPerson;
  String hotelCity;
  String availableFrom;
  String availableTo;
  public int getHotelId() {return hotelId; }
  public void setHotelId(int hotelId) {
    this.hotelId = hotelId; 
  public String getHotelName() {return hotelName;}
  public void setHotelName(String hotelName) {
    this.hotelName = hotelName;
  public BigDecimal getRatePerPerson() {
    return   ratePerPerson;
  public void setRatePerPerson(BigDecimal ratePerPerson){
    this.ratePerPerson = ratePerPerson;
  public String getHotelCity() {return hotelCity;}
  public void setHotelCity(String hotelCity) {
    this.hotelCity = hotelCity;
  public String getAvailableFrom() {return availableFrom;}
  public void setAvailableFrom(String availableFrom){
    this.availableFrom = availableFrom;
  public String getAvailableTo() {return availableTo;}
  public void setAvailableTo(String availableTo){ 
    this.availableTo = availableTo;

The current Camel version I am using does not support automatically mapping ResultSet to POJO, so I wrote a helper class to do it. (Don't worry, Camel version 2.14 will have this.) 

package org.blogdemo.travelagency.promotionhotel;

import java.math.BigDecimal;
import java.text.SimpleDateFormat;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;

public class ResortDataConvertor {

  public List processResultSet(List> resultset){
  List avaliableResorts = new ArrayList();
    for(Map obj:resultset){
      ResortInfo resortInfo = new ResortInfo();
      resortInfo.setAvailableFrom(new SimpleDateFormat("MM-dd-yyyy HH:mm:ss").format(obj.get("AVAILABLEFROM")));
      resortInfo.setAvailableTo(new SimpleDateFormat("MM-dd-yyyy HH:mm:ss").format(obj.get("AVAILABLETO")));
   return avaliableResorts;

Because of the restriction in the business flow, we can only return one hotel at a time, create the java class that randomly choose one hotel, and also create a default one if no criteria is matched in database.

package org.blogdemo.travelagency.promotionhotel;

import java.math.BigDecimal;
import java.util.List;
import java.util.Random;
import org.apache.camel.Exchange;
import org.apache.camel.Processor;

public class RandomHotelBean implements Processor{
  public void process(Exchange exchange) throws Exception {
    List resorts = (List)exchange.getIn().getBody();
    ResortInfo resort;    
    if(resorts == null || resorts.size() == 0){
      resort = new ResortInfo();
      resort.setHotelName("The Grand Default Hotel");
      resort.setRatePerPerson(new BigDecimal("109.99"));
      Random rand = new Random();
      int  n = rand.nextInt(resorts.size());
      resort = resorts.get(n);

Don't forget to register the beans too. 

And this is the route. 

If you would like to add test, here is how you do,
package org.blogdemo.travelagency.promtionhotel;

import javax.jms.ConnectionFactory;
import static org.apache.camel.component.jms.JmsComponent.jmsComponentAutoAcknowledge;

import org.apache.camel.CamelContext;
import org.apache.camel.test.blueprint.CamelBlueprintTestSupport;
import org.junit.Test;

public class RouteTest extends CamelBlueprintTestSupport {
  protected String componentName = "activemq";
    protected String getBlueprintDescriptor() {
        return "/OSGI-INF/blueprint/blueprint.xml";
    protected CamelContext createCamelContext() throws Exception {
        CamelContext camelContext = super.createCamelContext();

        ConnectionFactory connectionFactory = CamelJmsTestHelper.createConnectionFactory();
        camelContext.addComponent(componentName, jmsComponentAutoAcknowledge(connectionFactory));

        return camelContext;

    public void testRoute() throws Exception {
     String out = template.requestBody("activemq:queue:requestHotel", "{\"startCity\":\"London\",\"startDate\":\"2015-01-01\",\"endDate\":\"2015-03-01\"}", String.class);
     assertEquals("{\"hotelId\":201,\"hotelName\":\"The Grand Default Hotel\",\"ratePerPerson\":109.99,\"hotelCity\":null,\"availableFrom\":\"2015-01-01\",\"availableTo\":\"2015-03-01\"}", out);


For more details steps, such as setting up dependencies, see here.

Next time we will take a look persistence with JPA.

For more detail side in BPM Suite, please click here to Eric Schabell's post.

Micro Services Migration Story with JBoss BPM Travel Agency
Part One: Introduction and Installation
Part Two: Moving towards Microservices
Part Three: Retrieving Data with JDBC 


Hi Christi I was able to implement your code in camel:run, But I am unable to deploy the project in fuse 6.1 OSGI container.

I am getting following exception

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'camel-12': Invocat
ion of init method failed; nested exception is org.springframework.beans.factory.CannotLoadBeanClassExcept
ion: Cannot find class [org.apache.camel.component.jpa.JpaComponent] for bean with name 'jpa' defined in
RL [bundle://491.0:0/META-INF/spring/camel-context.xml];

Thanks for help in advance.


Popular posts from this blog

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

RHTE - Supercharge your integration services

Red Hat Tech Exchange has taken place in Vietnam, Ho Chi Minh city two weeks ago, it is a great event held by Red Hat in Asia Pacific Region. It is open to all Red Hat partners who are interested in learning what Red Hat is doing recently, see what the trend of the open source world, basically it is a great event to share your knowledge and experience, to meet other enthusiastic people.

I am very fortunate to talk in this great event, to talk about the things I have been working on and even discuss it with many. Also got lots of great ideas too. So here are the slide.

My first talk was with Thomas Qvarnström about how to handle large size data in JBoss Fuse and how JBoss Data Grid can help in the situation.

Here is the agenda of the talk, we will be talk about this in the up coming webinar on 24th Sept.

Integration often involves storing, retrieving, and transforming data. Using a traditional database in your integration is likely to becomes a bottleneck that is expensive and hard to …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …