[CONF] Apache Camel > Event Driven Consumer

[confluence]

Event Driven Consumer Page edited by Babak Vahdat Changes (2) h3. Event Driven Consumer Camel supports the [Event Driven Consumer|http://www.enterpriseintegrationpatterns.com/EventDrivenConsumer.html] Consumer|http://www.eaipatterns.com/EventDrivenConsumer.html] from the [EIP patterns|Enterprise Integration 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. !http://www.enterpriseintegrationpatterns.com/img/EventDrivenConsumerSolution.gif! !http://www.eaipatterns.com/img/EventDrivenConsumerSolution.gif! The Event Driven Consumer is implemented by consumers implementing the [Processor|http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Processor.html] interface which is invoked by the [Message Endpoint] when a [Message] is available for processing. ... Full Content 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. For more details see Message Message Endpoint 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. Change Notification Preferences View Online | View Changes | Add Comment