Yes, we use beanRef(MyBean.class.getName(), "myMethodName") in all our routes. The bean is not configured via spring and until 2.11.0 a new instance of it was created for each camel message. In 2.13.0 the same instance is used for each camel message.
Short answer: Yes :) kind regards, Christoph Claus Ibsen-2 wrote > Hi > > And your beanRef you refer to is a FQN class name (not a bean id in a > spring xml file or something) and you want a new instance of that FQN > class to be created each time (eg prototype scoped) and therefore want > cache disabled? > > And what you see in Camel 2.13.x is that its no longer prototype scoped? > > Is that correct? -- View this message in context: http://camel.465427.n5.nabble.com/beanRef-is-caching-instances-in-camel-2-13-0-unwanted-behavior-tp5751335p5751395.html Sent from the Camel - Users mailing list archive at Nabble.com.
