Page History

...

Else, if more customization 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 customization, e.g.:

...

As part of the Camel bean integration, Camel comes with a set of annotations that are seamlessly supported by Camel CDI. So you can use any of these annotations in your CDI beans, e.g.:

@PropertyInject("key")
String value;

@Inject
@ConfigProperty(name = "key")
String value;

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

...

You can refer to CDI beans, either by type or name, From from the Camel DSL, e.g. with , using the Java Camel DSL:

class MyBean {
	//...
}
 
from("direct:inbound").bean(MyBean.class);

...

@Named("foo")
class MyNamedBean {
	//...
}
 
from("direct:inbound")
  .bean("foo");

Referring Beans From Endpoint URIs

When configuring endpoints using the URI syntax you can refer to beans in the Registry using the # notation. If the URI parameter value starts with a a # sign sign then Camel CDI will lookup for a bean of the given type by name, e.g.:

from("jms:queue:{{destination}}?transacted=true&transactionManager=#jtaTransactionManager")
  .to("...");

Having the following CDI bean qualified with @Named("jtaTransactionManager"):

...

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

...