2.3. Working with Camel on EAP Subsystem

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."));
    }
}

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;

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");
   }
  }

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() {
        // ...
    }
}

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;