[
https://issues.apache.org/jira/browse/FELIX-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-1484.
------------------------------------
Resolution: Fixed
Fix Version/s: configadmin-1.0.12
Closing this fixed. The actual implementation of fixing this is tracked in
FELIX-1488
> Dynamically bound configuration must be reset to null after target bundle is
> uninstalled.
> -----------------------------------------------------------------------------------------
>
> Key: FELIX-1484
> URL: https://issues.apache.org/jira/browse/FELIX-1484
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Affects Versions: configadmin-1.0.10
> Reporter: Ikuo YAMASAKI
> Assignee: Felix Meschberger
> Fix For: configadmin-1.0.12
>
>
> 1. create a configuration with pid1 and null location.
> 2. bundleA, who has locationA, registers ManagedService with pid1.
> 3. Then the configuration MUST be "dynamically bound" to bundleA, where the
> location of the configuration is set to locationA.
> Here, If bundleA is uninstalled, the configuration MUST be unbound again; the
> location of the configuration MUST be set to null again.
> See 104.4.1 Location Binding in R4.2 cmpn
> ----
> A null location parameter may be used to create Configuration objects that
> are not bound. In this case, the objects become bound to a specific location
> the first time that they are used by a bundle. When this dynamically bound
> bundle is subsequently uninstalled, the Configuration object's bundle
> location
> must be set to null again so it can be bound again later.
> ----
> However, the location still keeps bundleA in Felix Cm impl.
> That seems a bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
