No, the ServiceTracker takes care of the problem that there are always
two cases:
1. A service is already registered. this means you will not get an
event on the service listener. You must get it from the registry.
2. A service will be registered, you get an event
Tracking these two cases is tricky and that is why we developed the
Service Tracker. Now you see only 3 events:
1. Adding
2. Modified properties
3. Removing
A LOT simpler ... in the early days of OSGi we found that we were all
making our own abstractions to handle this tracking so we decided it
was better if we standardized it.
Kind regards,
Peter Kriens
AM> Thank you for your assistance...
AM> xmmm...your responses makes me think in terms of ServiceListener vs
AM> ServiceTracker (Pros n Cons).
AM> What do I lose if I use ServiceTracker? A part of control on the system
AM> response over some events?
AM> My best Regards,
AM> Aggelos
AM> _______________________________________________
AM> OSGi Developer Mail List
AM> [email protected]
AM> http://www2.osgi.org/mailman/listinfo/osgi-dev
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drιzιry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
