Re: OSGI service lookup

Hi Ralph, On Sat, 2 Apr 2022 at 11:02, Ralph Goers wrote: > > Ok. But what does that mean with regard to the 3 options Piotr listed? Declarative Services is backward compatible, so if someone declares a provider using DS, it will be detected by our current logic. Since we want (do we?) to mainta

Re: OSGI service lookup

Ok. But what does that mean with regard to the 3 options Piotr listed? Ralph > On Apr 1, 2022, at 4:37 PM, Matt Sicker wrote: > > OSGi services are the lowest level primitive they have besides bundles and > wires. The declarative services runtime was my preferred system when I was > using OSG

Re: OSGI service lookup

OSGi services are the lowest level primitive they have besides bundles and wires. The declarative services runtime was my preferred system when I was using OSGi several years ago, though I don’t know if that’s the preferred standard. — Matt Sicker > On Apr 1, 2022, at 18:16, Ralph Goers wrote

Re: OSGI service lookup

Actually, I’d prefer the one that is the most OSGi-like so that it is easily usable by OSGi users (if there are any). It seems to me that what we are currently doing fits that the best - requiring them to be OSGi services. Ralph > On Apr 1, 2022, at 1:23 PM, Matt Sicker wrote: > > I'd most p

Re: OSGI service lookup

I'd most prefer whichever approach is most compatible with the non-OSGi use case. For anything OSGi-specific that needs to be added to our metadata, it would be best provided in a format that's easily merged with other metadata (e.g., via the manifest.mf file). The DSR idea still sounds pretty good

OSGI service lookup

Hello, In my initial version of the release 2.x `ServiceLoaderUtil` I used an external OSGI bundle (`osgi-resource-locator`) to lookup services in other bundles (cf. source code