[STANBOL-464] The Bundle Provider MUST NOT uninstall resources if a Bundle is STOPPED

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0-incubating
• Component/s: Commons
• Assignee: Rupert Westenthaler
• Reporter: Rupert Westenthaler
• Created: 18/Jan/12 17:45
• Updated: 09/May/12 13:47
• Resolved: 19/Jan/12 12:51

Description

The Bundle Provider adds support to the Apache Sling OSGI Installer Framework that installs Resources provided by OSGI Bundles.

Currently Bundle Events are processed like follows:

• STARTED: all installable resources will be installed
• STOPPED: all installable resource will be uninstalled
• UPDATED: all installable resources will be first uninstalled and than installed

The issue is with uninstalling resources if a Bundle is STOPPED because this event is also sent for all bundles if the OSGI Environment is shutting down. The affected resources will be installed again on the next start however this behavior is not intended and can cause a lot of side effects such as that Services that are created by installed configurations will get different Service PIDs on every restart.

To solve this uninstalling of resources MUST only be performed if a Bundle is UNINSTALLED. This event is only sent if a Bundle is programmatic or manually removed form the OSGI environment and can be never sent by a normal life cycle activity.

Thanks to David Riccitelli in helping me to identify this as source for a lot of hart to track down bugs within Stanbol.

Issue Links

• is superceded by: STANBOL-532 Bundle Provide (Sling installer plugin) should again uninstall resources if Bundles are STOPPED. However it MUST NOT uninstall resoruces when the System Bundle not Active