Skip to main content

Red Hat JBoss Fuse - Getting Started Home Loan Demo version 6.2 Part 5

This is the 5th part of my getting started demo for JBoss FUSE 6.2, an update from my old demo project.  For people that are getting started to know Fuse, and wants to get their hands dirty and develop a JBoss Fuse project.

There is a series of blogs/videos, you can find the previous post here:

The story behind the home loan demo is to prepare housing appraisals base on the content given real estate vendor. The appraisal needs to talk to local database, external google map API and also provide information through a web Restful API. We have divided this project into 4 independent integration applications, deploy in a distrusted environment, each handle single functions, and using message broker as the asynchronous medium to pass the message and data around.

First part of demo was to take in and process the information, first we separates the 2 kinds of files, because they are handled differently. And send it to separate messaging broker.
Second demo was about processing the customer data, by reading the xml file and store it into a existing database table.
Third part starts to process housing data by getting number of schools surrounding the house address via SAAS. Forth part does the actual housing value appraisal and store it into database.

Fifth demo, the vendors are asking for an service that provides all the data with the updated appraised house value back to them. And they are requesting if the information can be provided through a Restful Web service. It's a piece of cake for JBoss Fuse developer to expose an service via Web Service, we simply setup and configure the endpoints. Previously we need to state the interface with Java interfaces or classes, but with the latest new Rest DSL in Camel, we can simply set the endpoint through simple XML setting.

You will find detail instruction in the video.

In this demo,  you will learn:

Rest DSL to expose Restful Endpoint services, map the Restful service using Camel-Servlet. 
Allow end users to define REST services using a REST style, it builds Rest endpoints in Camel routes. But the actual REST transport is supported by components that has native REST integration

<rest path="/summaryservice">
    <get uri="/nationalID/{clientId}">
      <to uri="direct:customerSummary"/>

<restConfiguration component="servlet" contextPath="/homeloan" host="localhost" port="9999" bindingMode="json" >
  <dataFormatProperty key="prettyPrint" value="true"/>


SQL Endpoint 
The sql: component allows you to work with databases using JDBC queries.

You can also find the source project in my github.


MimerPlusPlus said…
Thanks for a great introduction to Fuse!

I've tried to use it as inspiration for a Camel blueprint application, but im running into problems, when trying to jUnit test my application. I would like to test my endpoints by extending CamelBlueprintTestSupport, but when i do that, my tests halt with the exception:

java.lang.RuntimeException: Gave up waiting for service (objectClass=org.apache.camel.CamelContext)
at org.apache.camel.test.blueprint.CamelBlueprintHelper.getOsgiService(
at org.apache.camel.test.blueprint.CamelBlueprintHelper.getOsgiService(

After waiting for a while with the following output:

[ Blueprint Extender: 2] BlueprintContainerImpl INFO Bundle XXX is waiting for dependencies [(objectClass=org.osgi.service.http.HttpService)]

It seem that the test Blueprint, does not give me a HttpService

Could you possibly add a few jUnit tests to you exaple code?

Christina Lin said…
You will need to look at Pax Exam to do the testing.

Popular posts from this blog

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 …

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 …

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …