Hi Felix, On 2 July 2012 11:13, Felix Meschberger <[email protected]> wrote: > Am 01.07.2012 um 22:06 schrieb David Bosschaert: >> 2. The Subsystem-Content lists all the dependencies of the project. >> However, because some of the bundles for this subsystem weren't >> developed with OSGi in mind, the start ordering is significant. I >> don't know of an easy way to generate this so currently it's hardcoded >> and hence duplicated. Also note that fragments obviously don't have a >> start-order. > > Just wondering: How could start order be forced in OSGi ? > > IIRC there is no such thing as start ordering because such an order can never > be guaranteed -- start levels only help to a certain degree.
The start-order is an attribute defined in the Subsystems spec section 134.12.1. It simply defines the order in which the bundles are started within that subsystem. In my case I need this because my subsystem uses some bundles that weren't originally written for OSGi and they do some static initialization that has to be ordered in a certain way to function correctly. Cheers, David
