On 2018-10-01T12:42:18 -0400
Raymond Auge <[email protected]> wrote:

> I'm not sure I can agree with your position on the use of Service Loader
> Mediator.
> 
> We, as an OSGi community, have no choice but to make certain accommodations
> for the development of libraries which are not always going to be used in
> OSGi but DO want to support it in the least intrusive way. Service Loader
> Mediator is exactly that way.
> 
> All, I can suggest is to have a little faith. Aries Spi-Fly is a well used
> and very efficient piece of software that does the absolute minimal amount
> of bytecode manipulation. With the most recent release you can even get
> around ordering issues by using the framework extension (also it's only a
> single bundle with no dependencies) on an R7 framework (both of equinox and
> felix have R7 releases).

Apologies if it came across as overly pessimist. I was just a bit
disappointed by the realization that it's going to become increasingly
necessary to employ bytecode rewriting just to use foundational
Java libraries in OSGi (because JPMS has pushed ServiceLoader into the
foreground, and people are more likely to employ it now that they know
it exists).

Right now I'm using a custom runtime based on Felix, and I use boot
delegation to expose SLF4J to code running inside the container. This
sidesteps the problem, but it's hardly pretty.

-- 
Mark Raynsford | http://www.io7m.com

Attachment: pgpEQONaSJloA.pgp
Description: OpenPGP digital signature

Reply via email to