This page describes the SPI Fly component.
The SPI Fly component is aimed at providing OSGi support for JRE SPI mechanisms, including the usage of
META-INF/services and similar methods.
SPI Fly is the Reference Implementation of the OSGi ServiceLoader Mediator specification, chapter 133 in the OSGi Enterprise Specification, available from version 5.
java.util.ServiceLoader.load(), other similar methods such as
sun.misc.Service.providers() and also other static finder methods such as the
FactoryFinder.find() methods try to locate 'service' implementations by looking for resources in the META-INF/services directory of all the jars visible to the Thread Context ClassLoader (TCCL).
There are a number of issues with the above mechanisms when used in OSGi:
The Thread Context ClassLoader is not defined in general in an OSGi context. It can and has to be set by the caller and OSGi cannot generally enforce that.
A bundle can’t Import-Package META-INF/services as potentially many bundles will contain this pseudo-package and the OSGi framework will only bind a single exporter to an importer for a given package.
Instantiating an SPI provider generally requires access to internal implementation classes, by exporting these classes an implementing bundle would break its encapsulation.
Even if an implementation class was exported, importing this class in a consumer bundle would bind it to the specific implementation package provided, which violates the principle of loose coupling.
Bundles have a dynamic life-cycle which means that provided services could disappear when a bundle is updated or uninstalled. The java.util.ServiceLoader API does not provide a mechanism to inform service consumers of such an event.
The SPI Fly project makes it possible to use existing code that uses
ServiceLoader.load() and similar mechanisms under OSGi.
In order to make ServiceLoader (and other similar SPI or plugin mechanisms) work under OSGi, calling code can be woven to set the TCCL to the appropriate providers very briefly, only for the duration of the call. The SPI Fly component does precisely this.
SPI Fly supports two modes of operation:
OSGi Specification compliant configuration. This is based on OSGi generic requirements and capabilities and provides portability across implementations of this specification. However, it only covers
java.util.ServiceLoader. Find it here.
If you need to handle cases other than
java.util.ServiceLoader, such as the various FactoryFinders,
javax.sound.sampled.AudioSystemor others that use the TCCL to find an implementation, you can use the SPI Fly-specific configuration.
Additionally, services found in the META-INF/services location in opted-in bundles will be registered in the OSGi Service Registry so that OSGi-aware consumers can simply find them there. This is supported in both the spec-compliant as well as the proprietary configuration modes. Each such service is registered in the OSGi Service Registry with the serviceloader.mediator service registration property set.
To use SPI Fly you need to decide whether to use the dynamic or static weaving version. More information about this can be found in the usage section.
For use with dynamic weaving:
For use with static weaving:
The code can be found in http://svn.apache.org/repos/asf/aries/trunk/spi-fly.
To build, use Maven 3.x and run
All the details surrounding this type of configuration are covered in the OSGi Enterprise Specification (from version 5) chapter 133. This section provides a short overview.
SPI provider bundles opt in to being registered by specifying a requirement on the
This is done by adding the following Bundle Manifest header.
Without this they will not be considered by SPI Fly:
Additionally, they need to provide capabilities for all the APIs that are exposed through this mechanism, for example:
While this example omits it, it is advisable to specify
uses constraints on the Provide-Capability header, to ensure consistent class spaces.
spi-fly-example-provider2-bundle for an example of a spec-compliant provider.
An SPI consumer (i.e.
a bundle using the
java.util.ServiceLoader.load() API) needs to specify required capabilities in the Required-Capability Manifest header.
Two different types of requirements must be specified:
A requirement on the SPI Fly processing mechanism. This is stated as follows +
osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"+ without this requirement the bundle will not be considered for processing.
A requirement on the SPI that needs to be provided through this mechanism, for example +
osgi.serviceloader; filter:="(osgi.serviceloader=org.apache.aries.spifly.mysvc.MySPIProvider)";cardinality:=multiple+ Note that the
cardinalitydirective is specified to allow multiple bundles to provide the requested capability, allowing provided services to come from more than one provider bundle.
All requirements are combined into a single Require-Capability header:
spi-fly-example-client2-bundle for an example of a spec-compliant consumer.
This section describes how to use SPI Fly’s proprietary configuration mechanism.
It provides more features, but doesn’t provide the portability that spec-compliance configuration gives.
If you are only using SPI Fly with
java.util.ServiceLoader or you are only using the provided services through the OSGi Service Registry, then consider using the spec-compliant configuration for portability.
First for all, SPI Fly needs to be made aware of any bundles that provide the services.
These bundles are made visible through the TCCL for the duration of the
ServiceLoader.load() (or similar) call.
To mark a bundle as a Provider, set the
SPI-Provider manifest header:
*SPI-Provider: ** will consider all providers found in the META-INF/services directory and register them.
SPI-Provider: org.acme.MySvc1, org.acme.MySvc2 will only consider MySvc1 and MySvc2.
Additionally services found in META-INF/services are registered in the OSGi Service Registry.
SPI-Provider header can either be set in the providing bundle itself or in a wrapper bundle that holds the original unmodified jar containing the provider internally as a on the
spi-fly-example-provider1-bundle for an example of a provider using this type of configuration.
Service consumers also need to opt in to the process.
To specify a consumer, add the
SPI-Consumer manifest header to the client bundle.
This header will opt-in the bundle to the weaving process where for the duration of the specified call the TCCL will be set to the matching provider bundle(s).
Some example SPI-Consumer headers are:
*SPI-Consumer: ** This is a shorthand for
java.util.ServiceLoader#load(java.lang.Class)and will automatically weave all
SPI-Consumer: java.util.ServiceLoader#load(java.lang.Class[org.apache.aries.mytest.MySPI]) Only process calls to
ServiceLoader.load(Class)when it is called with
SPI-Consumer: javax.xml.parsers.DocumentBuilderFactory#newInstance() weave clients that call
SPI-Consumer: org.foo.Foo#someMthd(),org.bar.Bar#myMethod() weave calls to
spi-fly-example-client1-bundle for an example of a consumer using this type of configuration.
SPI Fly can be used for most SPI provider/lookup systems that use the TCCL pattern to obtain implementations. However, some cases some special treatment is needed. This special treatment is often needed when the API itself does not match the name of the resources in META-INF/services, java.util.ServiceLoader is such a case, however SPI-Fly has built-in knowledge of ServiceLoader. Known APIs that require special treatment are listed below:
javax.imageio.spi.ServiceRegistry: This class is very much like java.util.ServiceLoader in that it can load any kind of API implementation. While SPI Fly knows about ServiceLoader and treats it specially, the ServiceRegistry class currently does not have special treatment. It can still be made to work but this requires the following header in the provider bundle:
SPI-Provider: javax.imageio.spi.ServiceRegistryon the client side you can use
javax.sound.sampled.AudioSystem: This class uses sun.misc.Service under the covers (via com.sun.media.sound.JDK13Services) which is a predecessor to java.util.ServiceLoader. There is no special treatment for sun.misc.Service in SPI Fly (yet), but the AudioSystem.getAudioInputStream() API can be made to work by explicitly listing it in the provider bundle (the one that contains the relevant META-INF/services resources):
SPI-Provider: javax.sound.sampled.AudioSystemon the consumer side you can use `SPI-Consumer: javax.sound.sampled.AudioSystem#getAudioInputStream `
If you have an OSGi 4.3 (or higher) compliant framework that supports WeavingHooks you can use the dynamic weaving approach.
If you have an pre-4.3 OSGi framework or don’t want to use bytecode weaving at runtime you can use the static weaving approach.
g! lb START LEVEL 1 ID|State |Level|Name 0|Active | 0|System Bundle (5.0.1) ... bundles 1-4 are framework/console internal ones ... 5|Active | 1|ASM all classes (5.0.4) 6|Active | 1|Apache Aries Util (1.1.1) 7|Active | 1|Apache Aries SPI Fly Dynamic Weaving Bundle
Note that, as with any OSGi Bundle that uses the OSGi 4.3 WeavingHooks, the weaver bundle (
org.apache.aries.spifly.dynamic.bundle in the SPI Fly case) needs to be active before any bundles that need to be dynamically woven.
OSGi Start Levels can provide a mechanism to control this.
For static use, you need to weave the client bundle before installing it into the system.
The modification changes the byte code around
java.util.ServiceLoader.load() or other calls in the bundle and inserts calls to set the correct ThreadContextClassLoader around it.
Provider bundles are still handled dynamically.
The easiest way to invoke the static weaver is to take the
org.apache.aries.spifly.static.tool jar with dependencies.
Then run the static tool on any bundle that needs processing:
java -jar org.apache.aries.spifly.static.tool-1.0.2-jar-with-dependencies.jar mybundle.jar
This will produce a second bundle with the same name with the _spifly suffix appended, so in this case the generated bundle will be called mybundle_spifly.jar.
At runtime, install the
org.apache.aries.spifly.static.bundle into the system, like the dynamic weaving bundle it has a dependency on the Aries Util bundle:
g! lb START LEVEL 1 ID|State |Level|Name 0|Active | 0|System Bundle (5.0.1) ... bundles 1-4 are framework/console internal ones ... 5|Active | 1|Apache Aries Util (1.1.1) 6|Active | 1|Apache Aries SPI Fly Static Weaving Bundle
Then install and start the statically woven bundle into the system.
spi-fly-examples directory contains a number of example bundles that can be used for testing or experimenting.
The following modules can be found in this directory:
spi-fly-example-provider1-jar - a plain jar file providing an implementation of the SPI (via
spi-fly-example-provider1-bundle - a bundle that wraps the jar file from the previous bullet and specifies it in its Bundle-ClassPath. This example represents the common case where an existing SPI provider is wrapped as-is in an OSGi bundle. This example uses the SPI Fly proprietary configuration. osgi-bundle source
spi-fly-example-client1-jar - a plain jar using java.util.ServiceLoader.load() to obtain and invoke all services provided of a certain SPI. source
spi-fly-example-client1-bundle - a bundle that wraps the jar file from the previous bullet and lists it in its Bundle-ClassPath. This example represents the common case where an existing SPI consumer is wrapped as-is in an OSGi bundle. This example uses SPI Fly proprietary configuration. osgi-bundle source
spi-fly-example-provider-consumer-bundle - a bundle that is both a provider and a consumer at the same time. source
spi-fly-example-resource-provider-bundle and spi-fly-example-resource-client-bundle - these bundles show that SPI Fly can be used to control the TCCL in OSGi for any situation, in this case applied to resource loading via the TCCL. The provider bundle provides a resource used by the Foo.doit() API. The client bundle contains Foo.doit() and in there calls Thread.getContextClassLoader().getResource() to obtain the resource. The TCCL has visibility of the provider bundle because both bundles have the appropriate values set in the SPI-Provider and SPI-Consumer headers. Source here and here.
More information can be found at the following resources:
OSGi Service Loader Mediator specification. OSGi Enterprise specification, Chapter 133.
OSGi Blog article: http://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html