[
https://issues.apache.org/jira/browse/FELIX-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-1732.
------------------------------------
Resolution: Invalid
Components with static references are never reactivated due to service
registration and unregistration:
- once a static reference is bound it remains bound until the service is
unregistered or the component becomes deactivated for other reasons.
- a static reference not bound is not bound if the component is not reactivated
for other reasons.
Therefore this situation can never happen and thus this issue is invalid.
> Prevent repeated unneeded component reactivation
> ------------------------------------------------
>
> Key: FELIX-1732
> URL: https://issues.apache.org/jira/browse/FELIX-1732
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.0.8
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Consider a component A with two (or more) static, mandatory references R1 and
> R2. When A is activated, the references are not satisfied yet and the
> component is unsatisfied. Now services are registered and references R1 and
> R2 become satisifed. Since the bindings are static, A has to be stopped and
> restarted to bind the referenes.
> For this, two asynchronous reactivate tasks are scheduled. In certain
> situations now, the reactivation tasks might run only after both services are
> registered. That is the first reactivation task actually binds both
> references and the second reactivation task stops and restarts the component
> to no avail.
> Component reactivation should be enhanced to ensure reactivation only takes
> place if the reactivation reason is still present (e.g. unbound static
> reference to be bound).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
