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

["David Jencks (JIRA)" <ji...@apache.org>]

David Jencks created FELIX-3870:
-----------------------------------

             Summary: [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.6.4


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