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/01/17 20:02:22 UTC
[jira] [Reopened] (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 reopened FELIX-4022:
---------------------------------
The spec committee now appears to think that the "correct" behavior is only for namespace >= 1.3 and the "wrong" behavior is needed for namespace 1.1. and 1.2. I plan to add a DS configuration flag that can turn on "correct" behavior for namespace 1.1. and 1.2.
> [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.0
>
>
> 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.1.5#6160)