On Sun, Sep 23, 2012 at 1:51 AM, Raul Kripalani <r...@evosent.com> wrote: > Hi fellow riders, > > The async routing engine page in the docs [1] suggests that the SEDA > Producer is async. > I may be slightly confused, but I don't see the SedaProducer returning > "false" in its process() method at any point (overridden from > DefaultAsyncProducer). > > In fact, all unit tests that require the async routing engine to be in > place use a utility component called MyAsyncComponent, rather than SEDA. > > Am I missing something? >
No not totally. The seda component is on the roadmap for being improved for Camel 3.0 http://camel.apache.org/camel-30-roadmap.html There is a few spots where it could be improved less invasive, and then some areas where it may be a bit trickier. However currently I would assume the InOnly could be improved to use the async routine engine. The trickier part is the InOut with the timeout. For timeout we would need to either drop it completely. Or introduce a timeout handler to keep track of timeouts, and what follows. That is a bit trickier to do right. This is related to the Async Bridge EIP from the SMX 3.x JBI world http://servicemix.apache.org/servicemix-eip.html#servicemix-eip-AsyncBridge And as this pattern is good. It could be worthwhile to check up on what it would take to support the async routine engine to the fullest, and as well how to handle the timeout / correlation of replies etc. Hence why its scheduled for Camel 3.0. > [1] http://camel.apache.org/asynchronous-routing-engine.html > > Thanks! > Raúl. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
