Skip to main content

Red Hat JBoss Fuse - 3 ways to develop you Fuse application in JBoss EAP, XML route with JNDI

In this series post I am going to show the different ways of developing a Camel web application running in JBoss EAP.
  • Spring Framework
  • CDI with Java DSL
  • XML without Spring
To make things clear and easy, I will be using the exact same Camel route for all there different methods.What this Camel route does, is it starts up a timer that will log every 5 second, simple, easy, not much going on.

Before we start develop our simple camel route, we need to a base WAR project to work on, so first we need to create a WAR file, I am sure you must have a million way to create that, every one sort of have their own best practice for this. For me, in the example, I will create one with maven, using the webapp-javaee6 artifact. 

A. Create Project, select Maven Project, 

B. Click Next when you are at New Maven Project, and it will take you to the next step, select the webapp-javaee6 artifact.

C. Add your project name, and then click Next, you will have a ready to go WAR project in your JBoss Developer Studio. (Note, for my examples later, I am going to give them different project Names)

D. Add Camel dependency in the pom.xml file (do make sure you maven repo is configure properly pointing to http://repo.fusesource.com/nexus/content/repositories/releases)

    <!-- camel -->
    <dependency>
      <groupId>org.apache.camel</groupId>
      <artifactId>camel-core</artifactId>
      <version>2.15.1.redhat-621xxx</version>
      <scope>provided</scope>
    </dependency>


E. Optional, change your JDK version accordingly in pom.xml of the WAR project.




Camel Route without Spring

Sometimes we just don't want to rely on Spring or CDI, just to keep everything simple. Camel uses the JNDI registry to achieve this. So no spring library is needed nor do we have to enable the CDI framework in JavaEE. A perfect solution if you don't want any heavy framework involve.

  • Before we start, we are going to need another camel dependency, this is the package we need to scan and kickstart our camel route.
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-servletlistener</artifactId>
            <version>2.15.1.redhat-620133</version>
        </dependency>

Under webapp, we need to create the WEB-INF/web.xml file, as we need it to configure the listener that reading our Camel route and then kicks it off. Right click on Deployment Descriptor and choose Generate Deployment Descriptor Stub. It will create an empty web.xml file for you.




  • Add the location of your camel file, and the listener that register and kicks off the camel route in the web.xml

<context-param>
    <param-name>name</param-name>
    <param-value>MyCamel</param-value>
</context-param>
<context-param>
    <param-name>routeBuilder-MyRoute</param-name>
    <param-value>classpath:myfisrtcamel.xml</param-value>
</context-param>
<listener>
    <listener-class>org.apache.camel.component.servletlistener.JndiCamelServletContextListener</listener-class>
</listener>

  • This is what your web.xml will look like:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" version="3.0">
  <display-name>myjndidemo</display-name>
  
  <context-param>
    <param-name>name</param-name>
    <param-value>MyCamel</param-value>
  </context-param>
  <!-- location of Camel route xml files -->
  <context-param>
    <param-name>routeBuilder-MyRoute</param-name>
    <param-value>
    classpath:myfisrtcamel.xml
    </param-value>
  </context-param>

  <!-- the listener that kick-starts Camel -->
  <listener>
    <listener-class>org.apache.camel.component.servletlistener.JndiCamelServletContextListener</listener-class>
  </listener>
  
  <welcome-file-list>
    <welcome-file>index.html</welcome-file>
  </welcome-file-list>

</web-app>

  • Create folder called "resources" under main for Camel Route XML file.   



  • Then add the folder in the Class Path, right click on the project, and select Build Path, configure build path




  •  Check the resource folder we just created!




Create Camel route called "myfisrtcamel.xml", make sure choose the "Routes" framework. 


  • Within route, drag and drop timer and log component and configure them. 
    • Timer URI: timer:mytimer?period=5000
    • Log Message: JNDI EAP Camel Demo
  • This is what your XML look like: 
 <?xml version="1.0" encoding="UTF-8"?>
  <routes xmlns="http://camel.apache.org/schema/spring">
  <route>
    <from uri="timer:mytimer?period=5000"/>
    <log message="JNDI EAP Camel Demo"/>
  </route>
</routes>

  • And then we are done, ready to go. Run mvn clean install to generate the war file. 





  • Start up your JBoss EAP with Fuse subsystem enabled. If you are not sure how to do it, please take a look at this post. In side bin folder, start JBoss EAP with 
    • standalone.sh
    • standalone.bat
  • Go to http://localhost:9990/, login to admin console, under Runtime/

  • Click on Add, choose the war generated under the project target folder. Click Next, Next to deploy the application. 
  • Start up application by click on the En/Disable button. 


  • Switch to the log, you will find it's now printing the message "JNDI EAP Camel Demo" every 5 seconds.

Comments

Popular posts from this blog

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 …

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 …