Peter Kriens wrote > Isn't this easily handed by a little helper class? > But not by using DS - I could use something like the service tracker approach and that's simple to do - but I'm leaving the DS features here.
Carsten > 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 > -- Carsten Ziegeler [email protected] _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
