Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

2.3. Working with Camel on EAP Subsystem

Here are some basic examples that describe how the camel subsystem interacts with JBoss EAP configuration files.

2.3.1. Using a Camel Context
Copiar enlace

The CamelContext represents a single Camel routing rulebase. It contains all the routes of your application. You can have as many CamelContexts as necessary, provided they have different names.
Camel on EAP allows you to:
  • define a CamelContext as a part of the subsystem definition in the standalone.xml and domain.xml files
  • deploy them in a supported deployment artifact that includes the -camel-context.xml suffixed file
  • provide CamelContexts along with their routes via a RouteBuilder and the CDI integration
You can configure a CamelContext as a part of the subsystem definition this way: 
<route>
       <from uri="direct:start"/>
       <transform>
         <simple>Hello #{body}</simple>
       </transform>
     </route>
Copy to Clipboard Toggle word wrap
Also, you can consume a defined CamelContext two ways:
  • @injected via Camel-CDI
  • via JNDI tree

2.3.1.1. Example of a Context and a Route
Copiar enlace

The following example, describes a context along with an associated route provided via CDI and a RouteBuilder. It displays an application scoped bean that starts automatically, when you start an application. The @ContextName annotation provides a specific name to the CamelContext. 
@ApplicationScoped
@Startup
@ContextName("cdi-context")
public class HelloRouteBuilder extends RouteBuilder {

    @Inject
    HelloBean helloBean;

    @Override
    public void configure() throws Exception {
        from("direct:start").transform(body().prepend(helloBean.sayHello()).append(" user."));
    }
}
Copy to Clipboard Toggle word wrap

2.3.1.2. Configuring Camel Context using CDI Mechanism
Copiar enlace

Camel CDI automatically deploys and configures a CamelContext bean. After you initialise the CDI container, a CamelContext bean starts and instantiates automatically.
You can inject a CamelContext bean into the application as: 
@Inject
    @ContextName(cdi-context)
    private CamelContext context;
Copy to Clipboard Toggle word wrap

2.3.1.3. Configuring Camel Routes using CDI Mechanism
Copiar enlace

After you initialise the CDI container, Apache Camel CDI automatically collects all the RouteBuilder beans in the application, instantiates and add them to the CamelContext bean instance.
For example, you can add a camel route and declare a class in the following way: 
class MyRouteBean extends RouteBuilder {
 
    @Override
    public void configure() {
        from("jms:invoices").to("file:/invoices");
   }
  }
Copy to Clipboard Toggle word wrap

2.3.1.4. Customizing Camel Context
Copiar enlace

Apache Camel CDI provides @ContextName qualifier that allows you to change the name of the default CamelContext bean. For example, 
@ApplicationScoped
class CustomCamelContext extends DefaultCamelContext {
 
    @PostConstruct
    void customize() {
        // Set the Camel context name
        setName("custom");
        // Disable JMX
        disableJMX();
    }
 
    @PreDestroy
    void cleanUp() {
        // ...
    }
}
Copy to Clipboard Toggle word wrap
Note
You can use any CamelContext class to declare a custom camel context bean.

2.3.1.5. Supporting Multiple CamelContexts
Copiar enlace

You can declare any number of CamelContext beans in your application. The CDI qualifiers declared on these CamelContext beans are used to bind the Camel routes and other Camel primitives to the corresponding Camel contexts.
The CDI qualifiers declared on the CamelContext beans are also used to bind the corresponding Camel primitives. For example: 
@Inject
@ContextName("foo")
@Uri("direct:inbound")
ProducerTemplate producerTemplate;
 
@Inject
@BarContextQualifier
MockEndpoint outbound; // URI defaults to the member name, i.e. mock:outbound
 
@Inject
@ContextName("baz")
@Uri("direct:inbound")
Endpoint endpoint;
Copy to Clipboard Toggle word wrap

2.3.2. Camel Context Deployment
Copiar enlace

You can deploy a camel context to JBoss EAP two ways:
  • Use the -camel-context.xml suffix as a part of another supported deployment, such as a JAR, WAR, or EAR deployment
    This deployment may contain multiple -camel-context.xml files.
  • Use the -camel-context.xml suffix in a standalone XML file deployment by dropping the file into the EAP deployment directory
A deployed camel context is CDI injectable as: 
@Resource(name = "java:jboss/camel/context/mycontext")
    CamelContext camelContext;
Copy to Clipboard Toggle word wrap

2.3.3. Hawtio Web Console
Copiar enlace

HawtIO is a web application that runs in a JVM. You can start Hawtio on your machine:
  • deploy HawtIO as a WAR file
  • add some users to your management and application realms by using the following command: $ bin/add-user.sh
  • navigate to the http://localhost:8080/hawtio, the HawtIO login page appears
  • Click Camelin the top navigation bar to view all the running Camel Contexts
Apache Camel plugin allows you to browse all the running Camel applications in the current JVM. You can also view the following details:
  • list of all the running camel applications
  • detail information of each Camel Context such as Camel version number, runtime statics
  • list of all the routes and their runtime statistics in each camel application
  • manage the lifecycle of all camel applications and their routes
  • graphical representation of the running routes along with real time metrics
  • live tracing and debugging of running routes
  • profile the running routes with real time runtime statics
  • browse and send messages to camel endpoint

2.3.4. Selecting Components
Copiar enlace

If you add nested component or component-module XML elements, then instead of the default list of Camel components, only the specified elements will be added to your deployment.
For example, 
<jboss umlns="urn:jboss:1.0">
<jboss-camel xmlns="urn:jboss:jboss-camel:1.0">
<component name="camel-ftp"/>
<component-module name="org.apache.camel.component.rss"/>
</jboss-camel>
</jboss>
Copy to Clipboard Toggle word wrap

2.3.5. Configuring Camel Subsystem
Copiar enlace

The Camel subsystem configuration may contain static system routes. However, these routes are started automatically. 
<route>
           <from uri="direct:start"/>
           <transform>
             <simple>Hello #{body}</simple>
           </transform>
         </route>
Copy to Clipboard Toggle word wrap

2.3.6. Configuring Camel Deployment
Copiar enlace

To make changes in the default configuration of your Camel deployment, you can edit either WEB-INF/jboss-all.xml or META-INF/jboss-all.xml configuration file.
Use a jboss-camel XML element within the jboss-all.xml file, to control the camel configuration.
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2026 Red HatVolver arriba