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 2014/05/03 03:13:14 UTC

[jira] [Resolved] (FELIX-4022) [DS] Deleting a configuration is supposed to deactivate the component unconditionally

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

David Jencks resolved FELIX-4022.
---------------------------------

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

Now spec compliant.  Silly deactivate-reactivate behavior for pre 1.3 namespaces unless you use the felix extension attribute
deleteCallsModify=true.   rev  1591423.

> [DS] Deleting a configuration is supposed to deactivate the component unconditionally
> -------------------------------------------------------------------------------------
>
>                 Key: FELIX-4022
>                 URL: https://issues.apache.org/jira/browse/FELIX-4022
>             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.8.2
>
>
> Spec 112.7.1 says if a configuration is deleted the component it configures must be deactivated (and presumably attempt reactivation if it's still satisfied).  Doesn't make sense to me, but there it is.



--
This message was sent by Atlassian JIRA
(v6.2#6252)