Chapter 2. Building Your Application on JBoss EAP

2.1. Overview

The following example demonstrates the use of camel-cdi component with Red Hat Fuse on EAP to integrate CDI beans with Camel routes.

In this example, a Camel route takes a message payload from a servlet HTTP GET request and passes it on to a direct endpoint. It then passes the payload onto a Camel CDI bean invocation to produce a message response and displays the output on the web browser page.

2.2. Running the Project

Before running the project, ensure that your set up includes maven and the application server with Red Hat Fuse. Perform the following steps to run your project:

  1. Start the application server in standalone mode:

    • For Linux: ${JBOSS_HOME}/bin/ -c standalone-full.xml
    • For Windows: %JBOSS_HOME%\bin\standalone.bat -c standalone-full.xml
  2. Build and deploy the project: mvn install -Pdeploy
  3. Now, browse to http://localhost:8080/example-camel-cdi/?name=World location. The following message Hello World from appears as an output on the web page. Also, you can view the Camel Route under the class as:

The bean DSL makes Camel look for a bean named helloBean in the bean registry. Also, the bean is available to Camel due to the SomeBean class. By using the @Named annotation, the camel-cdi adds the bean to the Camel bean registry.


public class SomeBean {

     public String someMethod(String name) throws Exception {

        return String.format("Hello %s from %s", name, InetAddress.getLocalHost().getHostAddress());



For more information, see $ EAP_HOME/quickstarts/camel/camel-cdi directory.

2.3. BOM file for JBoss EAP

The purpose of a Maven Bill of Materials (BOM) file is to provide a curated set of Maven dependency versions that work well together, saving you from having to define versions individually for every Maven artifact.

The Fuse BOM for JBoss EAP offers the following advantages:

  • Defines versions for Maven dependencies, so that you do not need to specify the version when you add a dependency to your POM.
  • Defines a set of curated dependencies that are fully tested and supported for a specific version of Fuse.
  • Simplifies upgrades of Fuse.

Only the set of dependencies defined by a Fuse BOM are supported by Red Hat.

To incorporate a BOM file into your Maven project, specify a dependencyManagement element in your project’s pom.xml file (or, possibly, in a parent POM file), as shown in the following example:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<project ...>

    <!-- configure the versions you want to use here -->



After specifying the BOM using the dependency management mechanism, it becomes possible to add Maven dependencies to your POM without specifying the version of the artifact. For example, to add a dependency for the camel-velocity component, you would add the following XML fragment to the dependencies element in your POM:


Note how the version element is omitted from this dependency definition.