Child pages
  • Event Driven Consumer

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

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.

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.


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

Code Block


Using the Spring XML Extensions

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


For more details see

Include Page
Using This Pattern
Using This Pattern