And please realize that you can never ensure you see start events ...
Using the bundle tracker as is ensures you get events for ALL bundles. Bundles
installed before or after you start running. This is the 'OSGi' way: NEVER RELY
ON ORDERING! :-)
If you can't use BundleTracker I am very curious what your requirements are?
Kind regards,
Peter Kriens
On 3 okt. 2013, at 19:47, Cristiano Gavião <[email protected]> wrote:
> Hello,
>
> I'm reading the RFC 204 and something is not clear in my mind.
> Initially I was thinking it would be useful to other specs that uses Extender
> concepts as OSGi JPA, DS or Blueprint that needs to be activated before any
> other bundle. But at the end of the reading I haven't sure... :)
>
> Could someone give some real, practical use cases of such spec/api ?
>
> thanks in advance.
>
> regards,
>
> Cristiano
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
