I am trying to upgrade to Camel 2.0 and running into a weird issue. Say i
have the following 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 cor
On Sat, Oct 10, 2009 at 4:28 PM, sasidharm wrote:
>
> I am trying to upgrade to Camel 2.0 and running into a weird issue. Say i
> have the following route:
>
>
>
>
>
> Here i am not specifying any method name explicitly for bean1 and I am
> depending on Camel's bean binding.
> T
Hi Stan,
This issue[1] has been fixed in the camel 2.1.0-SNAPSHOT :)
[1] http://issues.apache.org/activemq/browse/CAMEL-2060
Willem
Stan Lewis wrote:
On Sat, Oct 10, 2009 at 4:28 PM, sasidharm wrote:
I am trying to upgrade to Camel 2.0 and running into a weird issue. Say i
have the followin