Re: [osgi-dev] Names in the presence of multiple bundle versions

On 2017-07-22T17:46:56 +0100 Neil Bartlett wrote: > > On 22 Jul 2017, at 14:23, Mark Raynsford wrote: > > > > Yes, as am I. I used the example of multiple versions of the same jar > > resulting in multiple conflicting registrations of services trying

Re: [osgi-dev] Names in the presence of multiple bundle versions

Hi Justin, That’s exactly where I was going with that analogy. The equivalent of service.ranking for plumbers would presumably be their Yelp rating. And if you have multiple plumbers all with 5-star reviews then just pick any, it doesn’t matter! Neil > On 22 Jul 2017, at 14:04, Justin

Re: [osgi-dev] Names in the presence of multiple bundle versions

Hi Mark, > On 22 Jul 2017, at 14:23, Mark Raynsford wrote: > > 'Ello. > > I suspect we're in agreement, but I think there may've been a slight > miscommunication somewhere... > > On 2017-07-22T12:39:41 +0100 > Neil Bartlett wrote: >> >> I'm not

Re: [osgi-dev] Names in the presence of multiple bundle versions

On 2017-07-22T13:04:15 + Justin Edelson wrote: > Obviously you should pick the plumber with the highest service.ranking. > > Sorry, couldn't resist. http://academic.depauw.edu/aevans_web/HONR101-02/WebPages/Fall%202007/Kate%20W/Brazil%20the%20third/images/CS.jpg

Re: [osgi-dev] Names in the presence of multiple bundle versions

'Ello. I suspect we're in agreement, but I think there may've been a slight miscommunication somewhere... On 2017-07-22T12:39:41 +0100 Neil Bartlett wrote: > > I'm not talking at all about multiple versions of the same jar. I'm talking > about multiple providers of the

Re: [osgi-dev] Names in the presence of multiple bundle versions

Obviously you should pick the plumber with the highest service.ranking. Sorry, couldn't resist. On Sat, Jul 22, 2017 at 7:39 AM Neil Bartlett wrote: > I'm not talking at all about multiple versions of the same jar. I'm > talking about multiple providers of the same

Re: [osgi-dev] Names in the presence of multiple bundle versions

I'm not talking at all about multiple versions of the same jar. I'm talking about multiple providers of the same service, possibly even from different vendors. This happens just as easily under Service Loader as under OSGi. In your original email you asked: why does the consumer of PNG have to

Re: [osgi-dev] Names in the presence of multiple bundle versions

It still feels to me like you're putting the focus in the wrong place. The problem in this example is still fundamentally being caused by a poorly configured deployment containing unnecessary duplicates, so to me it sounds like you're saying that you want the system to be forgiving to bad

Re: [osgi-dev] Names in the presence of multiple bundle versions

On 2017-07-22T00:22:31 +0100 Neil Bartlett wrote: > Hello Mark, 'Ello. > > Tell me, why is this problem any harder under OSGi than with ServiceLoader?? > In both cases, anybody can install a bundle or a JAR that provides a service > with a name, and those names can

Re: [osgi-dev] Names in the presence of multiple bundle versions

On 2017-07-21T16:57:20 -0400 Raymond Auge wrote: > > I hate to say it because I've done exactly this on several occasions... :) > you get a List of tuples you can iterate over which will hold true to the > natural ordering of the services (via

Re: [osgi-dev] Names in the presence of multiple bundle versions

On 2017-07-21T20:14:51 + elias vasylenko wrote: > > As for multiple versions of the same bundle providing the same service, > well they would probably share the same service-ranking so that's no longer > a solution ... but then you have to wonder about the design

Re: [osgi-dev] Names in the presence of multiple bundle versions

Hello Mark, Tell me, why is this problem any harder under OSGi than with ServiceLoader?? In both cases, anybody can install a bundle or a JAR that provides a service with a name, and those names can collide. In both ServiceLoader and OSGi there is a simple rule for selecting a single instance

Re: [osgi-dev] Names in the presence of multiple bundle versions

I hate to say it because I've done exactly this on several occasions... But that is a bad design for the reasons you mentioned! However it happens enough that DS has something that can get your pretty close. The most recent version of the DS spec which added Field injection and in particular

Re: [osgi-dev] Names in the presence of multiple bundle versions

Hi, The normal strategy here would be to give priority to the ImageFormat service with the highest *service-ranking* and ignore others with the same name. Depending on how you set up your ImageFormats class you can even have DS inject services in ranking order to make it easier. Anyway there are