[FELIX-2456] Framework no longer fires UNRESOLVED event when a bundle is explicitly refreshed

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: framework-2.0.0, framework-2.0.1, framework-2.0.2, framework-2.0.3, framework-2.0.4, framework-2.0.5, framework-3.0.0, framework-3.0.1
• Fix Version/s: framework-3.0.7
• Component/s: Framework
• Assignee: Richard S. Hall
• Reporter: Richard S. Hall
• Created: 29/Jun/10 15:46
• Updated: 22/Dec/10 15:07
• Resolved: 07/Dec/10 21:33

Description

Between framework 1.8.x and 2.0.0, we removed the UNRESOLVED event when a bundle is explicitly refreshed. We need to put it back. It appears that when the code was restructured to have bundle uninstallation fire an UNRESOLVED event, it missed the case where a bundle was refreshed directly. Due to the uninstallation requirement, it is not possible to simply put the event firing back in place in refreshBundle() since it would result in multiple UNRESOLVED events being fired. We need to walk our way back from the refreshBundle() method to see who is using it and to also make sure setBundleStateAndNotify() is correctly called in all cases.