[
https://issues.apache.org/jira/browse/FELIX-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-2456.
----------------------------------
Resolution: Fixed
Assignee: Richard S. Hall
I modified refreshBundle() to fire an UNRESOLVED event if the bundle being
refreshed is not in the INSTALLED state. Hopefully, this fixes the issue.
> Framework no longer fires UNRESOLVED event when a bundle is explicitly
> refreshed
> --------------------------------------------------------------------------------
>
> Key: FELIX-2456
> URL: https://issues.apache.org/jira/browse/FELIX-2456
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: 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
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: framework-3.2.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
