felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FELIX-5054) Clean-up instance bound dependencies when component is destroyed
Date Mon, 30 Nov 2015 12:56:11 GMT

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

Pierre De Rop closed FELIX-5054.

> Clean-up instance bound dependencies when component is destroyed
> ----------------------------------------------------------------
>                 Key: FELIX-5054
>                 URL: https://issues.apache.org/jira/browse/FELIX-5054
>             Project: Felix
>          Issue Type: Improvement
>          Components: Dependency Manager
>    Affects Versions:  	org.apache.felix.dependencymanager-r5
>            Reporter: Pierre De Rop
>            Assignee: Pierre De Rop
>            Priority: Minor
>             Fix For: org.apache.felix.dependencymanager-r6
> Currently, when a component adds a dependency dynamically from its init() callback or
during the life of the component, then if the component goes through multiple init/destroy/init
cycles, then all instance bound dependencies must be manually removed from the destroy() callback.
> If the instance bound dependencies are not removed from destroy(), then the next time
the component is initialized again (init/destroy/init cycles), then the same instance bound
dependencies would then be re-added and duplicated.
> So, the intent of this improvement issue is just to automatically clean-up instance bound
dependencies when the component is destroyed. This way, if the component is initialized again,
then the earlier added instance bound dependencies are gone, and the init() method can re-add
them safely (we won't have duplicated instance bound dependencies in the component).

This message was sent by Atlassian JIRA

View raw message