Hi, Peter Kriens wrote > Well, they are not exclusive? I have used the ServiceTracker in other cases > where I had to do something special with n-ary services. No, they're definitly not exclusive - and currently I'm mixing them already - and of course this is not bad or something.
> > If you do OSGi specific things I do not think there is an issue to OSGi API. > Only code that wants to be completely independent of OSGi should work very > hard to be POJO. I like the OSGi API - and I have no problem depending on it :) I'm just trying to make a use case which I think is very common even easier :) I think it would be easy to add this to the spec and the implementation thereof would be easy as well; but it would make the usage of DS even simpler. Regards Carsten > > Kind regards, > > Peter Kriens > > On 14 jan 2011, at 12:16, Carsten Ziegeler wrote: > >> 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 > > > _______________________________________________ > 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
