Peter, Richard, Thanks for the replies. Your are right, homegrown bundles should not rely on this mechanism. But for practical purposes, some 3rd-party bundles I'm installing do and as such I was looking at the functionality as a bridge until those bundles get fixed.
I think I'll just need to solve it as a policy/process thing during deployment for problematic bundles. Thanks, Allen On Mon, Jan 19, 2009 at 11:04 PM, Peter Kriens <[email protected]>wrote: > OSGi has -no- installation order. If your bundles depend on this kind of > ordering (or startlevel ordering) they were not well designed and -will- > break one day. The reason is that a bundle can always get updated when the > system is running. If other bundles depend on this bundle without explicitly > specifying the dependencies, they are toast. > > Believe me, do no even try to control the start order. That is what we got > dynamic services for. > > Kind regards, > > Peter Kriens > > > > > > > On 19 jan 2009, at 21:32, Allen Lau wrote: > > Hi, >> >> Was wondering if there was a way to force the order of bundle installation >> with OBR? >> >> Basically I want to have the dependent bundles installed and optionally >> started first before the target bundle. >> >> For example. I have Bundle B1, B2, B3 >> >> where B1 depends on B2 which depends on B3. >> >> If I use OBR to deploy B1, I notice that most of the time B1 is installed >> first but doesn't it make more sense to have B3,B2 deployed first? >> >> Thanks, >> Allen >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
