felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (FELIX-4022) [DS] Deleting a configuration is supposed to deactivate the component unconditionally
Date Fri, 17 Jan 2014 19:02:22 GMT

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

Mime
View raw message