camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Pierre Bergamin <ja...@ractive.ch>
Subject Re: Intercept send to beanRef endpoint
Date Thu, 05 May 2011 09:34:41 GMT
Hello Romain

What exactly do you mean with the interceptProcessor()? I can't find any 
reference to such a construct.


Thanks,
James

Am 05.05.2011 09:48, schrieb Romain Manni-Bucau:
> Hi,
>
> i think it should stay like it (KISS), if you want to intercept you
> have to use an endpoints otherwise you are free to use endpoint,
> processors etc...
>
> another solution could be to add an interceptProcessor().
>
> - Romain
>
> 2011/5/5 Claus Ibsen<claus.ibsen@gmail.com>:
>> On Thu, May 5, 2011 at 9:19 AM, Jean-Pierre Bergamin<james@ractive.ch>  wrote:
>>> Hello camel users
>>>
>>> We are trying to intercept calls from being sent to a bean endpoint in a
>>> route that is declared as:
>>>   from("...").beanRef("myBean", "myMethod")
>>>
>>> The interception is declared as
>>> interceptSendToEndpoint("bean:myBean?method=myMethod"), but calls to myBean
>>> are not intercepted. When changing the route to
>>>   from("...").to("bean:myBean?method=myMethod")
>>> the interception works.
>>>
>>> Is there a way to use interceptSendToEndpoint together with beanRef()
>>> instead of "bean:myBean..."?
>>>
>> No. The beanRef is not an endpoint.
>> But maybe under the hood we can change that in camel-core so a beanRef
>> is a facade for sending a message to an endpoint.
>> Then the interceptor should work.
>>
>>
>>> Best regards,
>>> Jean-Pierre Bergamin
>>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> CamelOne 2011: http://fusesource.com/camelone2011/
>> Twitter: davsclaus
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>


Mime
View raw message