[
https://issues.apache.org/jira/browse/FELIX-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629832#comment-13629832
]
David Jencks commented on FELIX-4022:
-------------------------------------
there's a tck test for this behavior which is how I caught it (first I thought
the tck was wrong, and it does have a problem but not this). I think the
required behavior is dumb and probably due to lack of thought about wording in
the spec. I think an osgi bug might be a good idea.
> [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
