On Fri, Apr 24, 2009 at 2:36 PM, James Strachan <james.strac...@gmail.com> wrote: > 2009/4/24 Claus Ibsen <claus.ib...@gmail.com>: >> On Fri, Apr 24, 2009 at 11:23 AM, Guillaume Nodet <gno...@gmail.com> wrote: >>> The goal of the AsyncProcessor is to not block the calling thread when >>> using an InOut exchange mostly. >>> For example, if you invoke a web service which takes a long time to >>> answer, you don't really want the thread to be blocked for a few >>> seconds simply waiting for the answer: it just does not scale welll. >>> Not sure if the UnitOfWork stuff is sufficient to cover the InOut stuff. >> I do think we need a redesigned API for this that leverages the JDK >> concurrency stuff much more, e.g. the Future. >> >> And the current implementation is broken. And when you get the done >> callback, how do you get the result? > > Exchange.getOut() ? Yeah but then I have to use the "classic" Camel API. Not the 1 liners.
See the recent unit test that was committed: SedaAsyncProcessorTest Then we have a sample to work with. > > The Exchange object kinda is the 'future' object. > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus Apache Camel Reference Card: http://refcardz.dzone.com/refcardz/enterprise-integration
