Re: [osgi-dev] Making sure some bundles are started first

Start Levels can solve these problems but it’s best to use only as an optimisation rather than to enable functionality. I.e., make sure your bundles still work even if they are started in the “wrong” order, though perhaps with slightly poorer performance. 1st scenario seems to be fine… if you

Re: [osgi-dev] Making sure some bundles are started first

Start level would be a good fallback and technically simpler than system bundle fragment but maybe someone has a better idea. Christian On 28.10.2016 17:16, Jean-Baptiste Onofré wrote: Hi Christian I guess you don't want to use start level right ? Regards JB On Oct 28, 2016, at 15:25,

Re: [osgi-dev] Making sure some bundles are started first

For really low-level things consider using system.bundle fragments. In OSGi R6 system.bundle fragments are now allowed to have activators by specifying a ExtensionBundle-Activator header. See the R6 specification for the details, but in short the system.bundle fragments are activated at

[osgi-dev] Making sure some bundles are started first

There are some rare cases were I would like to make sure that certain bundles are started very early (or before other bundles). Two examples: - Karaf decanter logs messages, bundle and services events. The problem is that it will only start to do so when the decanter bundles are started. So

Re: [osgi-dev] osgi-dev Digest, Vol 120, Issue 93

Thanks, I'll stick with the old gogo shell for now and raise a bug. Regards, Liam O'Rourke On 27 October 2016 at 17:21, wrote: > Send osgi-dev mailing list submissions to > osgi-dev@mail.osgi.org > > To subscribe or unsubscribe via the World Wide Web,