It is not the change of https://issues.apache.org/jira/browse/CAMEL-6725 which is causing the problems, it's the change of https://issues.apache.org/jira/browse/CAMEL-6724.
I've changed the Registry.getBean() method to the old version and tested some of our routes again. Now the beans get not cached anymore. Should I create an issue for that? 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-tp5751335p5751345.html Sent from the Camel - Users mailing list archive at Nabble.com.
