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] [Updated] (FELIX-3718) [DS] deactivate might not move component state to unsatisfied
Date Wed, 31 Oct 2012 19:00:18 GMT

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

Felix Meschberger updated FELIX-3718:
-------------------------------------

    Fix Version/s:     (was: scr-1.8.0)
                   scr-1.6.2
    
> [DS] deactivate might not move component state to unsatisfied
> -------------------------------------------------------------
>
>                 Key: FELIX-3718
>                 URL: https://issues.apache.org/jira/browse/FELIX-3718
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.8.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-1.6.2
>
>
> After deactivating, we check to see if the state changed before moving to unsatisfied:
>             if ( acm.state() == this )
>             {
>                 acm.changeState( Unsatisfied.getInstance() );
>             }
> But the state might have been moved from Active to Registered meanwhile, so deactivate
would leave us in the Registered state.  Instead, check if the state is a satisfied state,
and if so, move it to unsatisfied.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message