Re: Service Loader Mediator (spifly)

Precisely. SPI-Fly (and the OSGi ServiceLoader Mediator spec, that it implements) are for those cases where you have to use ServiceLoader in OSGi. I think the best think to do here is to create a JIRA for it so that someone can pick it up and work on it. As Pierre says, it's not a bug as the

Re: Service Loader Mediator (spifly)

Understood, but you won't win that battle with Java EE APIs because for better or worse they mandate the use of service loader. The goal for Service Loader Mediator is still valid in this respect and seems the only viable course of action. The specific use case I'm working on are the Apache

Re: Service Loader Mediator (spifly)

The best option is, of course, to avoid using ServiceLoader as far as possible and to use injection to obtain the services. This way your Java SE injection container can use ServiceLoader (or whatever else it wants) and you can use OSGi services when in OSGi… Tim On 18 May 2018, at 21:41,

Re: Service Loader Mediator (spifly)

On Thu, May 17, 2018 at 10:52 AM, David Bosschaert < david.bosscha...@gmail.com> wrote: > Yeah, thinking more about it, the way it uses a weaving hook it currently > expects to be started before other bundles. Thanks @Pierre for reminding us > of that! > > I don't really like this ordering either

Re: Service Loader Mediator (spifly)

Yeah, thinking more about it, the way it uses a weaving hook it currently expects to be started before other bundles. Thanks @Pierre for reminding us of that! I don't really like this ordering either though. Just a couple of thoughts from my side: * if you use static weaving this problem goes

Re: Service Loader Mediator (spifly)

On Thu, May 17, 2018 at 9:44 AM, Pierre De Rop wrote: > Hi Ray, David; > > I was thinking that the org.apache.aries.spifly.dynamic.bundle should be > started before all other bundles ? > David, am I correct ? (see http://aries.apache.org/modules/spi-fly.html, > in section

Re: Service Loader Mediator (spifly)

Hi Ray, David; I was thinking that the org.apache.aries.spifly.dynamic.bundle should be started before all other bundles ? David, am I correct ? (see http://aries.apache.org/modules/spi-fly.html, in section "Use with Dynamic Weaving") cheers Pierre On Thu, May 17, 2018 at 12:42 PM, Raymond Auge

Re: Service Loader Mediator (spifly)

Ok, that's all I needed to hear. I'll file a bug report and try to make a test case. Thanks, - Ray On Thu, May 17, 2018 at 1:24 AM, David Bosschaert < david.bosscha...@gmail.com> wrote: > Hi Ray, > > Sounds like a bug to me. It shouldn't be restricted by start ordering. > Would it be possible

Re: Service Loader Mediator (spifly)

Hi Ray, Sounds like a bug to me. It shouldn't be restricted by start ordering. Would it be possible to file a bug? Best regards, David On 16 May 2018 at 18:38, Raymond Auge wrote: > Is the Service Loader Mediator known to be constrained by start ordering? > > In

Service Loader Mediator (spifly)

Is the Service Loader Mediator known to be constrained by start ordering? In other words, I'm finding that spifly is having issues when not "started" before other bundles that specify the requirements and or capabilities on osgi.serviceloader. -- *Raymond Augé*