Dependency on OSGi Blueprint

[kenwenzel]

Hello,

the infinispan OSGi bundles (at least infinispan-core and infinispan-tree) import the package

"org.osgi.service.blueprint [1.0.0,2.0.0)". This import makes them unusable in OSGi environments where

Blueprint services are unavailable (e.g. the basic Eclipse Platform with Equinox).

This dependency is automatically added by the maven-bundle-plugin because it detects the inclusion

of blueprint XML files.

Is it possible to either remove this Import-Package declaration or set its resolution to optional?

Thank you and best regards,

Ken

[sebastian.laskawiec]

Yes that would be possible. I've created a jira for it: [ISPN-6287] Make blueprint optional in OSGi manifests - JBoss Issue Tracker

mgencur - do you see any drawbacks?

[mgencur]

Hi Ken,

infinispan-core uses Blueprint to export some services related to configuration parsing or marshalling. Without Blueprint, it would not be possible to parse Infinispan configuration files. These services would have to be exported in a different way.

Martin

[sebastian.laskawiec]

Since we are not sure about your local environment - could you please help us a little bit and do an experiment?

Could you please:

• take the latest infinispan-embedded (or remote) artifact (it's called an Uber Jar - they should contain all necessary dependencies)
• modify MANIFEST.MF and make Blueprint optional
• check if you can start infinispan embedded (or connect to the remote cluster - depending on your use case)

[kenwenzel]

I included the modified infinispan-embedded bundle as well as a modified version of the infinispan-tree bundle in my OSGi environment.

But starting Infinispan fails with:

Caused by: java.lang.NullPointerException

    at org.osgi.util.tracker.ServiceTracker.<init>(ServiceTracker.java:184)

    at org.infinispan.commons.util.ServiceFinder.addOsgiServices(ServiceFinder.java:74)

    at org.infinispan.commons.util.ServiceFinder.load(ServiceFinder.java:49)

    at org.infinispan.util.ModuleProperties.resolveModuleLifecycles(ModuleProperties.java:41)

    ...

Best regards,

Ken

[sebastian.laskawiec]

In that case this is a new feature request (please track it in [ISPN-6287] Make blueprint optional in OSGi manifests - JBoss Issue Tracker). The easiest work around is to put Blueprint inside your container.

I also highly encourage you to adjust ServiceTracker and other bits to suite your needs and create a Pull Request.

Please contact me in case of any questions.