Yes they will have different object instances as its prototype scoped in the spring <bean> tag. In fact for each message Camel will lookup the bean in the spring app context and get a new instance.
You can tell Camel to cache the lookup by setting cache=true. See more at http://camel.apache.org/bean On Mon, Aug 12, 2013 at 5:42 PM, maheetw <maheshwari.saurab...@gmail.com> wrote: > Suppose i have following configuration > > <beans> > <bean id="dbwriter" class="com.test.WriterComponent" scope="prototype"> > </bean> > > <camelContext> > <route id = "ROUTE1"> > <from uri="direct:start"/> > <to uri="dbwriter:writer"/> > > <route id = "ROUTE2"> > <from uri="direct:start"/> > <to uri="dbwriter:writer"/> > </camelContext> > <beans> > > now since i am having dbwriter's scope as prototype then both the route > should have different object of bean of endpoint or same? > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Bean-s-scope-in-Camel-tp5737137p5737165.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
