camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: Asynchronous Remoting with Futures
Date Wed, 16 Mar 2011 07:24:19 GMT
If you are write your own component, you can use the camel async API[1] 
to do work asynchronously.

But as you are using the client API to send the request into the camel 
route, you need to leverage the Feature API[2]


On 3/16/11 2:13 AM, Harald Wellmann wrote:
> Am 15.03.2011 15:04, schrieb Claus Ibsen:
>> We could maybe detect the return type is a Future, and offer support
>> for that. I don't know how easy that would be.
>> That said its my impression that its only a few Camel end users who
>> needs to use the Future API.
> Hmm, if you don't use Futures, is there any other way of getting the
> asynchronous result of a proxy method call? Or is everybody directly
> using send/receive without service proxies?
> Some background for my question: I started looking into Camel as a
> possible replacement for Lingo, which we're using in our project in
> production. (Lingo is no longer maintained and only works for us with a
> bunch of patches.)
> But it seems that camel-jms only has a subset of Lingo's features (and
> possibly some others) - we're heavily using EventListener callbacks with
> Lingo. It may be a matter of taste whether or not Futures are preferable
> to listeners and callbacks, but as long as Camel supports neither, I
> guess we're stuck with Lingo.
> Best regards,
> Harald

Blog: (English)
Twitter: willemjiang

View raw message