Hi I have committed first cut of the new Async API to Camel trunk. See ticket CAMEL-1572 for svn revision and details.
The remaining work: - Migrate MulticastProcessor - Remove last piece of old API classes (2 interfaces) - Introduce Async DSL to replace Thread DSL and with clear intention of turning route into async mode and support thread pools using JDK executor service. - Support Jetty continuation with async Should we mark the old API in Camel 1.x as @deprecated? On Tue, May 5, 2009 at 4:48 PM, Claus Ibsen <[email protected]> wrote: > Hi > > Just wanted to keep you posted. > > Had some more work done to replace the old async API with the new API > in camel-core. > I basically got it all done except the MuticastProcessor as it would > take a bit more time to get done correctly. > I am thinking it should leverage the JDK CompletionService or the like > for keeping track on completed tasks. > > But for now I wanted to get the other parts working, and it looks good. > > The Thread DSL is to be replaced with a new Async DSL, so that is why > I am deleting it from the code base. > > And I am going to merge the async producer template into the regular > producer template so we have a single combined template for all > producer sync and async. > Its about 10 more methods. > > > > > On Tue, May 5, 2009 at 11:05 AM, Claus Ibsen <[email protected]> wrote: >> Hi >> >> I had some more time to work on this. >> I have attached a 2nd patch on the JIRA ticket 1572. >> >> This time the patch is only focusing on the AsyncProducerTemplate. I >> have added more methods to cover the most common methods use in >> producer template. >> With this an end user can initiate and async routing in Camel. >> >> If the user wants to use the regular Camel API (lookup endpoint, >> create exchange, create producer, process etc.) there is a helper >> method on AsyncProcessorHelper to initiate an async route as well. >> >> >> Any thoughts? >> >> >> >> On Fri, May 1, 2009 at 11:53 AM, Claus Ibsen <[email protected]> wrote: >>> I have committed a patch to trunk: >>> that resolves #1 (partly), #2 and #4 >>> >>> In #1 there are still two classes that needs a cleanup as well. >>> However they are core pieces in Camel, the Pipeline and >>> MulticastProcessor so they are left as is. When we have a new Async >>> API in place these classes can be fixed as well. >>> >>> I have also attached a prototype for a patch for the new async API >>> experiment I have done. See CAMEL-1572. >>> >>> -- >>> 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 >>> >> >> >> >> -- >> 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 >> Interview with me: >> http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress >> > > > > -- > 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 > Interview with me: > http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress > -- 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 Interview with me: http://architects.dzone.com/articles/interview-claus-ibsen-about?mz=7893-progress
