Event Driven Consumer

Camel supports the Event Driven Consumer from the EIP patterns. The default consumer model is event based (i.e. asynchronous) as this means that the Camel container can then manage pooling, threading and concurrency for you in a declarative manner.

image

The Event Driven Consumer is implemented by consumers implementing the Processor interface which is invoked by the Message Endpoint when a Message is available for processing.

Example

The following demonstrates a Processor defined in the Camel Registry which is invoked when an event occurs from a JMS queue.

Using the Fluent Builders

from("jms:queue:foo")
    .processRef("processor");

Using the Spring XML Extensions

<route>
    <from uri="jms:queue:foo"/>
    <to uri="processor"/>
</route>

For more details see:

Using This Pattern

If you would like to use this EIP Pattern then please read the Getting Started, you may also find the Architecture useful particularly the description of Endpoint and URIs. Then you could try out some of the Examples first before trying this pattern out.

Back to top