Skip to main content

Red Hat JBoss Fuse - Comparing different ways of Developing Fuse Application

Apache Camel in JBoss Fuse allow you to choose your favorite way to develop your integration application, and now it let you choose your favorite container to run it in. I put up a summary list of what each DSL are available, and made comparison between them. 

Available DSL in different Containers

Container
Domain Specific Language
Apache Karaf in JBoss Fuse
(OSGi Container)

Blueprint DSL (recommended)
Java DSL
Spring DSL
JBoss Enterprise Application Server
(JavaEE application Server)
Java DSL with CDI (recommended)
DSL with JNDI registry
Spring DSL

The reason to recommend blueprint in Karaf is that it provides a dependency injection framework in OSGi. The service lifecycle are monitored and managed, as it can dynamically shutdown or activate at anytime, blueprint can performs actions based on the state of each bundle, it is a much managed way to do in OSGi Container.
In Java EE container, JBoss Enterprise Application Platform, it also has a dependency injection framework – CDI. As the container will take care of the lifecycle of the beans.

There are no right and wrongs of which DSL you choose to work with, in fact you don’t have to choose just one, the beauty of JBoss Fuse is the freedom that it gives you to do what you prefer to do. Just make sure you choose the ones that you are most comfortable with. With that in mind, since I have posted the three different ways to develop Integration application on JBoss EAP, I have put together a small table that compares the difference between them.

Comparing Application development using different DSL on JBoss EAP 


Java DSL with CDI
Spring DSL
Route XML with JNDI Registry
Registry
CDI context managed by container
Application Context as Registry
JNDI Registry
Bean Register
CDI API using annotation
On xml
Implement CamelContextLifecycle <JndiRegistry>, initiate and bind bean in JNDI registry
Required Web.xml setting
N/A
N/A
Setup JndiCamelServletContextListener
Camel Context and Route Building
Implement RouteBuilder Class
Spring Framework XML with naming *-camel-context.xml
Route Framework and in web.xml set routeBuilder-MyRoute context parameter
DataSource Lookup
Lookup by CDI and provide via @Producer
Lookup using jee schema in Spring
Calling JNDI name in component
Messaging



JBDS Tooling
N/A
Yes
Yes
Route Description language
Java
XML
XML


These are base on one fact that the JBoss Fuse subsystem is correctly installed in JBoss EAP.

Comments

Zachariah Young said…
What about using Spring Boot to run camel routes?

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …