Hi, I am interested too to this topic.
I always used the start level for forcing the starting order of bundles. Of course you need to be sure that newly installed bundles gets a start level that is bigger than that applied to the bundles that have to start first. N. Da: osgi-dev-boun...@mail.osgi.org [mailto:osgi-dev-boun...@mail.osgi.org] Per conto di Christian Schneider Inviato: venerdì 28 ottobre 2016 17:20 A: OSGi Developer Mail List <osgi-dev@mail.osgi.org> Oggetto: 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, Christian Schneider <ch...@die-schneider.net<mailto:ch...@die-schneider.net>> wrote: 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 it misses some messages on startup. Decanter currently uses EventAdmin to communicate between modules. This introduces another point where messages can get lost during startup. - Simon Chemuil introduces an interesting Aspect framework Aspecio that can apply aspects to services. The problem is that it must be started before the services are present. Are there best practices for these use cases? Christian _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org<mailto:osgi-dev@mail.osgi.org> https://mail.osgi.org/mailman/listinfo/osgi-dev -- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
