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-1504) ComponentInstance implementation is reused accross reactivations
Date Fri, 21 Aug 2009 11:47:15 GMT

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

Felix Meschberger resolved FELIX-1504.

    Resolution: Fixed

In Rev. 806106 "moved" the "official" implementation of the ComponentInstance interface to
the ComponentContextImpl class. Instances of this class are recreated whenever the component
is activated. This ensures the ComponentInstance contract which has the same lifecycle requirement
as the ComponentContext.

> ComponentInstance implementation is reused accross reactivations
> ----------------------------------------------------------------
>                 Key: FELIX-1504
>                 URL: https://issues.apache.org/jira/browse/FELIX-1504
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR), Specification compliance
>    Affects Versions: scr-1.0.0, scr-1.0.2, scr-1.0.4, scr-1.0.6, scr-1.0.8
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: scr-1.2.0
> According to the specification of the ComponentInstance interface, instances of this
interface must not be reused after a component instance has been deactivated.
> Currently, the ComponentInstance interface is implemented by the AbstractComponentManager
class and thus is not replaced after the reactivation of a component.
> The implementation of the ComponentInstance interface has to be refactored to reflect
the life cycle of the actual component object (the object returned from ComponentInstance.getInstance().

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

View raw message