camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cgiera <christoph.gi...@mic-cust.com>
Subject beanRef is caching instances in camel 2.13.0 - unwanted behavior
Date Tue, 20 May 2014 08:49:17 GMT
Hello,

I've upgraded our application from camel 2.11.0 to camel 2.13.0.
First all looked fine, but now we are facing huge problems with all our
processes.

All our routes are caching the instances of our beans now, so we have a lot
of unwanted behavior in our application.

I've found an improvement point in jira
https://issues.apache.org/jira/browse/CAMEL-6725
which introduces the possibility of caching the instances. The documentation
says that it's defaulted to no, but even if i change our routes from
beanRef("classNameAsString","methodNameAsString") to
beanRef("classNameAsString","methodNameAsString", false) the instances of
the bean still get cached.

Could someone please check if my assumptions are correct and also has the
same behavior(then I think there is a bug)?


kind regards,
Christoph



--
View this message in context: http://camel.465427.n5.nabble.com/beanRef-is-caching-instances-in-camel-2-13-0-unwanted-behavior-tp5751335.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message