Hi, Albeit a bit clumsy it is also possible using an internal Sorted collection. The reference is converted to a multiple one and the ServiceReferences are kept in, say, a SortedSet such that the service with the highest ranking is always provided by sortedSet.iterator().next().
Regards Felix Am Freitag, den 14.01.2011, 11:34 +0100 schrieb Peter Kriens: > Isn't this easily handed by a little helper class? > > Kind regards, > > Peter Kriens > > On 14 jan 2011, at 11:27, Carsten Ziegeler wrote: > > > Hi, > > > > we're using declarative services a lot - it's usually sufficient and > > works pretty well :) > > > > The only drawback we're facing - and I've heard this from others as well > > - is the lack of proper support for references and the service ranking > > property: once a reference is bound it is not updated if a new component > > providing the same service but with a higher service ranking arrives. > > So, it gets more unpredictable and depends on the startup order of > > services to what service such a reference is bound. > > In these cases, you can't use DS. > > > > It would be great, to have a way to exactly define a reference that is > > always bound to the service with the highest ranking. To be compatible > > this has to be something new as we shouldn't change the current > > behaviour. So maybe adding a new optional property to the reference tag > > in the XML specifying if a rebound should happen due to service ranking > > or something along these lines. > > > > WDYT? > > > > Regards > > Carsten > > -- > > Carsten Ziegeler > > [email protected] > > _______________________________________________ > > 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 _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
