Hi Thomas, As the “vm-producer” and “vm-consumer” are decoupled, you have to address the context start order from outside (such as deploy time).
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On November 19, 2014 at 4:05:22 PM, Thomas Weinschenk (thomas.weinsch...@infoserve.endress.com) wrote: > Hi Claus, > > I don't see the problem on side of Karaf, Felix or OSGi at all or how the > contexts are deployed. The problem is that in a dynamic environment the > direct-vm consumer does not know the producers. Therefore the consumer > cannot trigger a restart of the other contexts. Especially if the contexts > are ‘chained’ like in my example. > > I suggest changing the behavior of the direct-vm component that a refresh of > the consumer is not forcing the producers to refresh as well. What do you > think? > Regards, > Thomas > > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/direct-vm-in-OSGI-how-to-handle-context-updates-tp5759259p5759310.html > > Sent from the Camel - Users mailing list archive at Nabble.com. >
