Hi, maybe there was a misunderstanding. I always wanted interception of dynamic routes created by a producer template but it is not working at all. While reading through the camel core code I recognized that camel routes builds static processor chains for endpoints handling and interception. Therefore I was asking for a possible workaround I actually can not see or if this is a missing feature worth adding into core.
I hope everything is clear now. ;-) Best, Benjamin Raul Kripalani <r...@evosent.com> schrieb: >Ben, > >I'm re-reading the thread and there seems to be some contradiction. > >At first you stated that you want to avoid the interception, but now >you >want it and it's not happening at all? > >Could you check, please? > >Thanks. > >Sent from a mobile device >On 24 Oct 2012 20:01, "Benjamin Graf" <benjamin.g...@gmx.net> wrote: > >> Hi folks, >> >> it seems that nobody has an answer to this question/problem? Is there >a >> proposal >> for dynamic creation of processor chains on the camel roadmap, yet? >Might >> be a >> topic worth thinking about! >> >> Best, >> Benjamin >> >> On 06.10.2012 08:28, Benjamin Graf wrote: >> > Hi Raúl, >> > >> > I tried to set explizit interception as mentioned, but it doesn't >work >> either. >> > If I read code right then interception is defined as a chain of >> processors when >> > route is initialized. I actually have not found any line of code in >> camel-core >> > where dynamic initialized ProducerTemplates are connected in that >> chains, maybe >> > not yet! :-) >> > >> > I already sent an example as requested by Christian. You might have >a >> look on it >> > to reproduce. It's build as spring osgi bundle so you have to use >> camel-springs >> > Main.class for standalone use. >> > >> > Thx so far. ;-) >> > >> > Best, >> > Benjamin >> > >> > On 04.10.2012 22:14, Raul Kripalani wrote: >> >> Interceptors live inside the Camel Context, and if the >ProducerTemplate >> is >> >> bound to the same context and the interception pattern matches, it >will >> >> also kick in for exchanges sent from the PT. >> >> >> >> Maybe you can set a condition using .when() so that only Exchanges >*not >> >> carrying a specific header* (e.g. 'FromProducerTemplate') are >ultimately >> >> intercepted. >> >> >> >> Then you set this header on all Exchanges sent via the >ProducerTemplate >> and >> >> you're interceptor should ignore them. >> >> >> >> Check out the second code example in the InterceptSendToEndpoint >doc >> >> section [1]. It shows how to use .when(). >> >> >> >> [1] >> >http://camel.apache.org/intercept.html#Intercept-InterceptSendToEndpoint >> >> >> >> Hope that helps, >> >> >> >> *Raúl Kripalani* >> >> Apache Camel Committer >> >> Enterprise Architect, Program Manager, Open Source Integration >> specialist >> >> http://about.me/raulkripalani | >> http://www.linkedin.com/in/raulkripalani >> >> http://blog.raulkr.net | twitter: @raulvk ><http://twitter.com/raulvk> >> >> >> >> On Thu, Oct 4, 2012 at 8:07 PM, Benjamin Graf ><benjamin.g...@gmx.net> >> wrote: >> >> >> >>> Hi everybody, >> >>> >> >>> I actually have a problem with a route using a producertemplate >as a >> >>> splitter to >> >>> send several exchanges. Unfortunately the ProducerTemplate seems >to to >> be >> >>> interceptable by my written Interceptor. Does anybody know how I >might >> >>> workaround this? >> >>> >> >>> Thx >> >>> Benjamin >> >>> >> >>> >> >> -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
