[
https://issues.apache.org/jira/browse/FELIX-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14567245#comment-14567245
]
Christian Schneider commented on FELIX-4907:
--------------------------------------------
I think this behaviour is good as it allows the updated method to clean up.
For example I use the same behaviour outside DM in plain OSGi with config
admin. I create a class when config is available and destroy it when the config
is null.
So if updated is called with null when then bundle is stopped this allows to
clean up without adding some special callback when the bundle stops. It is
simply the same behaviour as if the user deletes the config. So +1 for keeping
this functionality. On the other hand it of course makes sense to have a test
that checks for it and kind of documents the behaviour.
> ConfigurationDependency calls updated(null) when component is stopped.
> ----------------------------------------------------------------------
>
> Key: FELIX-4907
> URL: https://issues.apache.org/jira/browse/FELIX-4907
> Project: Felix
> Issue Type: Bug
> Components: Dependency Manager
> Affects Versions: org.apache.felix.dependencymanager-r3
> Reporter: Pierre De Rop
> Assignee: Pierre De Rop
> Fix For: org.apache.felix.dependencymanager-r4
>
>
> When a component has a Configuration Dependency, the updated callback is
> invoked with a null Dictionary when the omponent is stopped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
