[ARIES-957] SPIFly: Service Providers ignored if bundle is not active

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0

Environment

o.a.a.spifly.dynamic.bundle - 1.0.0-SNAPSHOT
Eclipse 4.2

• Assignee: Unassigned
• Reporter: Kevin Milburn
• Created: 05/Nov/12 12:54
• Updated: 15/Jan/19 20:14

Description

Bundles which provide services (through SPI-Provides or Provide-Capability) are not processed unless the bundle is activated, requiring explicity activation rather than lazy activation.

The providerBundleTracker in BaseActivator should track Installed, Resolved, Starting and Active bundles (same as the consumerBundleTracker).

With the ProviderBundleTrackerCustomizer as it current works, calls to bundle.getBundleContext() may result in a null pointer if the bundle is not active.

With Eclipse, a bundle with the Bundle-ActivationPolicy: lazy will become actived while processing the services (e.g. on bundle.loadClass()), resulting in a valid bundleContext. Bundles without this header will return null.

Issue Links

• is related to: ARIES-1814 Solve the start order limitations with SPI Fly