You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2013/02/07 08:37:12 UTC

[jira] [Resolved] (FELIX-3870) [DS] confusing logic around determining if modified method can be called on config update

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

David Jencks resolved FELIX-3870.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: scr-1.6.4)
                   scr-1.8.0

fixed by 1438383 and 1438607
                
> [DS] confusing logic around determining if modified method can be called on config update
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-3870
>                 URL: https://issues.apache.org/jira/browse/FELIX-3870
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.6.4
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: scr-1.8.0
>
>
> There are some logic problems in the code deciding if the modified method can be called.  We're seeing deactivation/reactivation if a config update happens while a component instance is being created.  Also the target filters are reset before we compare whether they have changed in a way to allow dynamic update.
> First step is to straighten out the logic.
> Second step will be to assure that the spec constraint that activate/modify/deactivate cannot be called concurrently is satisfied.

--
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