[jira] Resolved: (FELIX-1178) Component may remain deactivated after a reference has been unregistered and registered again

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved FELIX-1178.
--------------------------------------

    Resolution: Fixed

Applied fix in Rev. 778511 for AbstractComponentManager and Rev. 778512 for DependencyManager.

The fix is to add a pendingDeactivation flag as described in the issue summary.

> Component may remain deactivated after a reference has been unregistered and registered again
> ---------------------------------------------------------------------------------------------
>
>                 Key: FELIX-1178
>                 URL: https://issues.apache.org/jira/browse/FELIX-1178
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.0.8
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: scr-1.0.10
>
>
> If a static/mandatory reference of a component is unregistered, the component is scheduled to be deactivated. If the reference is registered again before the refering component is deactivated, the component is not activated again (since its state is still active or deactivating instead of unsatisifed).
> A flag should be added, which is set when the component is scheduled to be deactivated. If this flag is set when the component might have to be activated, the component is scheduled for activation. Scheduling the activation clears this flag. The flag is also cleared as soon as the component has been deactivated. If the component should be scheduled for deactivation and the flag is set, the component is not scheduled for deactivation again.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.