felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FELIX-1943) Component Factory not deactivated if required reference unregistered
Date Mon, 14 Dec 2009 10:10:18 GMT

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

Felix Meschberger resolved FELIX-1943.
--------------------------------------

    Resolution: Fixed

In Rev. 890260: Ensure components which are not satisfied any longer if a service is unregistered
are deactivated. Before this would only happen if the component had the service bound, which
is not always the case (for example for ComponentFactory components).


> Component Factory not deactivated if required reference unregistered
> --------------------------------------------------------------------
>
>                 Key: FELIX-1943
>                 URL: https://issues.apache.org/jira/browse/FELIX-1943
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR), Specification compliance
>    Affects Versions: scr-1.2.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For:  scr-1.2.2
>
>
> When a component factory becomes unsatisifed, it must be deactivated and switch to the
UNSATISIFED state until it becomes satisifed again. Currently this does not happen because
the component factory does not really bind to the references but the DependencyManager.serviceRemoved
method only may deactivate a component if the unregistering service is actually bound.
> The serviceRemoved method must be enhanced to also check whether a component is becoming
unsatisifed even in this case.

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


Mime
View raw message