camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stan Lewis <gashcr...@gmail.com>
Subject Re: Bean endpoint in a route is holding reference to the last used methodName and does not invoke Camel's Bean binding
Date Tue, 13 Oct 2009 19:30:13 GMT
On Sat, Oct 10, 2009 at 4:28 PM, sasidharm <sasi.mukkamala@gmail.com> wrote:

>
> I am trying to upgrade to Camel 2.0 and running into a weird issue. Say i
> have the following route:
> <route>
>        <from uri="jms:jms/queue/>
>        <process ref="someProcessor" />
>        <to uri="bean1" />
> </route>
>
> Here i am not specifying any method name explicitly for bean1 and I am
> depending on Camel's bean binding.
> The first time a message is pulled from jms:jms/queue, the correct method
> (say method1) is invoked on bean1 (matching the exchange's body to the
> bean's method parameter types). From next time onwards, Camel is holding
> the
> reference to method1 in bean1's BeanProcessor and is invoking
> bean1.method1() for all subsequent messages pulled from jms:jms/queue.
>
>
What kind of messages are we talking about here, just text messages?  Also
what parameter types do you have defined in your bean?  It would be handy to
get a test case to investigate further.



> I am noticing this behavior only in Camel 2.0. It was working fine until
> Camel 1.6.
>
> Btw, I am using InOut exchange pattern when seding the messages to
> jms:jms/queue.
>
> Can anyone please help!!!
>
>
> --
> View this message in context:
> http://www.nabble.com/Bean-endpoint-in-a-route-is-holding-reference-to-the-last-used-methodName-and-does-not-invoke-Camel%27s-Bean-binding-tp25838095p25838095.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message