[
https://issues.apache.org/jira/browse/FELIX-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-301.
-------------------------------------
Resolution: Fixed
Fortunately, it was not necessary to modify the API. Instead the implementation
of the FilePersistenceManager.getDictionaries() method has been changed to
return all dictionaries and to only check for file names if the service.pid
property is actually set.
After this, the ConfigurationManager.bundleChanged had to be adapted to accept
any dictionary and use it as a Configuration or Factory depending on whether
the service.pid property is present. To enable creating a Factory instance from
a dictionary, the factory.pid property is introduced in Factory dictionaries.
After these changes, all persistent dicitonaries are scanned and checked for
the bundle location of the uninstalled bundle. For each dictionary, a check in
the internal cache is first done to directly modify the cache object and store
that.
Fixed in Rev. 544741
> Factory Configurations not unbound on bundle uninstall
> ------------------------------------------------------
>
> Key: FELIX-301
> URL: https://issues.apache.org/jira/browse/FELIX-301
> Project: Felix
> Issue Type: Bug
> Components: Configuration Admin
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 1.0.0
>
>
> According to the spec. configurations must be unbound from their bundle
> location when the respective bundle is uninstalled. Currently the
> Configuration Admin Service implementation does not respect this requirement
> (in fact, this is a known fact according to the TODO comment ...)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
