[CONF] Apache Camel > Asynchronous Routing Engine

[confluence]

Asynchronous Routing Engine Page edited by Claus Ibsen Changes (3) ... - [JBI] (both consumer and producer) - [NMR] (both consumer and producer) - [CXF] (requires *Camel 2.5*) (only producer) - [CXF] *Camel 2.5:* (only producer) - [Jetty] (both consumer and producer) - [Netty] (only producer) - [JMS] *Camel 2.5:* (only producer for [Request Reply] messaging over JMS) When we say a component is supported, that means, the component is leveraging the asynchronous model. For example [Jetty] uses continuations and the async http client to be fully asynchronous and non blocked. That means no threads will ever be blocked while waiting for a reply. ... Full Content Asynchronous Routing Engine Available as of Camel 2.4 As of Camel 2.4 the asynchronous routing engine is back and kicking. All the Enterprise Integration Patterns is supported as well a selected number of Components: JBI (both consumer and producer) NMR (both consumer and producer) CXF Camel 2.5: (only producer) Jetty (both consumer and producer) Netty (only producer) JMS Camel 2.5: (only producer for Request Reply messaging over JMS) When we say a component is supported, that means, the component is leveraging the asynchronous model. For example Jetty uses continuations and the async http client to be fully asynchronous and non blocked. That means no threads will ever be blocked while waiting for a reply. In the future additional Components will be supported as well where it's applicable. Background information See Asynchronous Processing for additional information and the concepts behind the asynchronous model. Change Notification Preferences View Online | View Changes | Add Comment