[ARIES-983] The BundleHookBundleTracker has an invalid logic wrt initially tracked bundles

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: util-1.1.0
• Component/s: Util
• Assignee: Guillaume Nodet
• Reporter: Guillaume Nodet
• Created: 07/Dec/12 12:38
• Updated: 02/May/13 02:30
• Resolved: 13/Dec/12 10:06

Description

The bundle tracker does not register the hook service before tracking bundles which means it can miss events when starting.
In addition, some methods are not overriden from BundleTracker and may lead to bad results if called.
The only reason for BundleHookBundleTracker to override BundleTracker is to be easily manipulated the same way, but given the internals are changed, all the methods must be redefined because they all call a private (thus not overridable) method.

Issue Links

• relates to: FELIX-3806 Some bundle events are sent to SynchronousBundleListeners without holding the bundle lock which can cause the event to be delivered out of order
• relates to: ARIES-1005 BundleHookBundleTracker throws Exception when close()-method is called twice
• relates to: ARIES-1005 BundleHookBundleTracker throws Exception when close()-method is called twice