Hi Paul, Start order within a single start level is undefined. If you really need a specific start order then you can use OSGi start levels to achieve this, but it is generally better to avoid that if possible.
The Aries Subsystem bundles should not require a particular starting order. Could you maybe create an Aries issue [1] for this? I guess it's easy to reproduce by just installing the subsystem bundles and then starting them in the 'wrong' order? Thanks, David [1] https://issues.apache.org/jira/browse/ARIES On 8 September 2015 at 07:27, Holly Cummins <[email protected]> wrote: > Interesting, thanks for sharing the solution! > > On 8 Sep 2015, at 05:53, Paul F Fraser <[email protected]> wrote: > > Hi, > > Seems that bundle start order is important. Raspi scrambled the start order > of bundles. > > Forcing start order to be the same as other devices caused raspi to create > the synthesized bundle. > > Paul > > > On 7/09/2015 8:07 PM, Paul F Fraser wrote: > > Hi, > > Using subsystems on osx, linux and windows (laptops),the synthesized bundle > is created. > > org.osgi.service.subsystem.region.context.0 (1.0.0) > > On a raspberry pi (armhf) this is not created. > > Can someone point me to the code I should be checking to see where the > problem could be. > > Or is there any known reason why this might be so? > > Regards > > Paul Fraser > >
