Thx. For the future, it could be interesting that the message (exchange) is intercepted and processed asynchronously without impacting the existing route.
On Fri, Aug 27, 2010 at 11:49 AM, Yiannis Mavroukakis < [email protected]> wrote: > Hmm according to this > http://camel.apache.org/intercept.html > > It emulates AOP, as it applies to all the From routes. In your instance it > will be intercepted once as the page for Intercept details, right after the > from("direct"). > > On 27 August 2010 10:36, Charles Moulliard <[email protected]> wrote: > > > Hi, > > > > I would like to know when we use the InterceptFrom strategy if we create > > two > > exchanges (one for the interceptor and the other for the route) and if > the > > processing of the two exchanges is done in parallel or in > > asynchronous way ? > > > > ex : > > > > InterceptFrom().to(log) > > > > from("direct").to("bean:service"); > > > > Regards, > > > > Charles Moulliard > > > > Senior Enterprise Architect (J2EE, .NET, SOA) > > Apache Camel - Karaf - ServiceMix Committer > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Blog : http://cmoulliard.blogspot.com | Twitter : > > http://twitter.com/cmoulliard > > Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: > cmoulliard > > >
