You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/08/11 07:09:49 UTC

[jira] [Closed] (FELIX-4964) [DS] Reactivate component at most once per service event

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

Carsten Ziegeler closed FELIX-4964.
-----------------------------------

> [DS] Reactivate component at most once per service event
> --------------------------------------------------------
>
>                 Key: FELIX-4964
>                 URL: https://issues.apache.org/jira/browse/FELIX-4964
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-2.0.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-2.0.0
>
>
> When a component has several references to the same service (most likely scenario is field references for object, properties, service ref all for the same service) and a service event results in the component being deactivated and activated (such as a static reference being replaced by another) then we should only reactivate the component instance once.
> The solution I have in mind involves distributing events to the service trackers for the components in a bundle through the BundleComponentActivator and tracking the components that need to be activated with the event.  Once all the relevant service trackers have been notified, we can try to activate all the components relevant to that service event.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)