You can open bugs against the OSGi API in the OSGi bugzilla system at https://www.osgi.org/bugzilla/ --
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [email protected] office: +1 386 848 1781 mobile: +1 386 848 3788 From: Will Horn <[email protected]> To: OSGi Developer Mail List <[email protected]> Date: 2009/09/01 18:27 Subject: Re: [osgi-dev] Staying up to date with the highest ranked instance of a service Sent by: [email protected] On Mon, Aug 31, 2009 at 2:32 AM, Peter Kriens <[email protected]> wrote: Why not just the service object in the callback, addingService provides it to you? I want to stay up to date on the highest ranked service. That service in addingService is the one currently being added, which is yet not reflected in ServiceTracker#getService(). Thanks BJ and AZ for the tips. BundleContext#getServiceReference returns the highest ranked service during the callbacks so I can use that to get what I need. But then I have still run into a bug/feature that BundleContext#getServiceReference is not the highest ranked service in cases where a service is modified to increase its ranking. I have already posted on the Equinox list ( http://dev.eclipse.org/newslists/news.eclipse.technology.equinox/msg06711.html ) about this, but maybe this mailing list is the more appropriate place to discuss it? -Will_______________________________________________ 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
