Page History

...

...

Else, if more customisation is needed, any CamelContext class can be used to declare a custom Camel context bean. Then, the @PostConstruct and @PreDestroy lifecycle callbacks can be done to do the customisation, e.g.:

@ApplicationScoped
class CustomCamelContext extends DefaultCamelContext {

    @PostConstruct
    void customize() {
        // Set the Camel context name
        setName("custom");
        // Disable JMX
        disableJMX();
    }

    @PreDestroy
    void cleanUp() {
        // ...
    }
}

Producer and disposer methods can also be used as well to customize the Camel context bean, e.g.:

...

@PropertyInject("propertykey")
String propertyvalue;

@Inject
@ConfigProperty(name = "messagekey")
String propertyvalue;

@Produce(uri = "mock:outbound")
ProducerTemplate producer;

@Inject
@Uri("direct:outbound")
ProducerTemplate producer;

@EndpointInject(uri = "direct:inbound")
Endpoint endpoint;

@Inject
@Uri("direct:inbound")
Endpoint endpoint;

@EndpointInject(uri = "direct:inbound", context = "foo")
Endpoint contextEndpoint;

@Inject
@ContextName("foo")
@Uri("direct:inbound")
Endpoint contextEndpoint;

@BeanInject
MyBean bean;

@Inject
MyBean bean;

@BeanInject("foo")
MyBean bean;

@Inject
@Named("foo")
MyBean bean;

@Consume(uri = "seda:inbound")
void consume(@Body String body) {
    //...
}

...

Camel events to CDI events

Available as of Camel 2.17

Camel provides a set of management events that can be subscribed to for listening to Camel context, service, route and exchange events. Camel CDI seamlessly translates these Camel events into CDI events that can be observed using CDI observer methods, e.g.:

...

Similarly, the @Default qualifier can be used to observe Camel events for the default Camel context if multiples contexts exist, e.g.:

void onExchangeCompleted(@Observes @Default ExchangeCompletedEvent event) {
    // Called after the exchange 'event.getExchange()' processing has completed
}

Note that the support for Camel events translation into CDI events is only activated if observer methods listening for Camel events are detected in the deployment, and that per Camel context.

CDI events endpoint

Available as of Camel 2.17

The CDI event endpoint bridges the CDI events with the Camel routes so that CDI events can be seamlessly observed / consumed (resp. produced / fired) from Camel consumers (resp. by Camel producers).

...

This is equivalent to writing:

...

@Inject
Event<String> event;

from("direct:event").process(new Processor() {
    @Override
    public void process(Exchange exchange) {
        event.fire(exchange.getBody(String.class));
    }
}).log("CDI event sent: ${body}");

@Inject
Event<String> event;

from("direct:event")
    .process(exchange -> event.fire(exchange.getIn().getBody(String.class)))
    .log("CDI event sent: ${body}");

...

• camel-example-cdi-metrics - illustrates the integration between Camel, Dropwizard Metrics and CDI,
• camel-example-cdi-properties - illustrates the integration between Camel, DeltaSpike and CDI for configuration properties,
• camel-example-cdi-osgi - a CDI application using the SJMS component that can be executed inside an OSGi container using PAX CDI,
• camel-example-cdi-rest-servlet - illustrates the Camel REST DSL being used in a Web application that uses CDI as dependency injection framework,
• camel-example-widget-gadget-cdi - The Widget and Gadget use-case from the EIP book implemented in Java with CDI dependency Injection.

See Also

• CDI Web site
• CDI ecosystem
• Going further with CDI (See Camel CDI section)