The key word is potentially ... normally the log service will be there
or shortly. It is highly unlikely that it will -ever- have to wait. So
in the unlikely case you take a performance hit, but things keep on
working.
I just needed to demonstrate the waitForService as well.
However, I'll add a comment about the synchronous behavior of service
tracker.
Kind regards,
Peter Kriens
BH> I am not sure that is such a great example. The log method block for
BH> potentialy a very long time and thus can impede the ServiceEvent deliver
BH> for HttpService. The ServiceTrackerCustomizer methods are called from the
BH> ServiceListener inside ServiceTracker and should complete quickly.
BH> BJ Hargrave
BH> Senior Technical Staff Member, IBM
BH> OSGi Fellow and CTO of the OSGi Alliance
BH> [EMAIL PROTECTED]
BH> office: +1 386 848 1781
BH> mobile: +1 386 848 3788
BH> Peter Kriens <[EMAIL PROTECTED]>
BH> Sent by: [EMAIL PROTECTED]
BH> 02/23/2007 04:11 AM
BH> Please respond to
BH> OSGi Developer Mail List <[email protected]>
BH> To
BH> Aggelos Mpimpoudis <[EMAIL PROTECTED]>
BH> cc
BH> [email protected]
BH> Subject
BH> Re: [osgi-dev] Re: Knopflerfish and Eclipse
BH> If you need another example with the service tracker look at:
BH> http://www.aqute.biz/Snippets/Tracker
BH> There are also some similar examples.
BH> Kind regards,
BH> Peter Kriens
BH> _______________________________________________
BH> OSGi Developer Mail List
BH> [email protected]
BH> 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
