You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2013/04/12 07:25:18 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13629807#comment-13629807 ]
Felix Meschberger commented on FELIX-4022:
------------------------------------------
Yes, it says that in the first section and it sounds wrong.
I think it is more like that configuration deletion should be handled like configuration update which may involve reactivation of the component without the configuration. See the last sentence in the section:
"SCR must attempt to satisfy the component configuration with the updated component properties."
Unless the current implementation is completely wrong, I doubt we should do anything.
> [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 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