[
https://issues.apache.org/jira/browse/FELIX-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158567#comment-17158567
]
Guillaume Nodet commented on FELIX-6103:
----------------------------------------
Yes, the 1-arg {{getConfiguration(pid)}} method call should only be used from
the bundle which is using the configuration directly. Any other usage, such as
the one here, should use either {{getConfiguration(pid, "?")}} or
{{getConfiguration(pid, null)}}.
> ConfigInstaller, when using NotCachablePersistenceManager, can restore cached
> stale properties
> ----------------------------------------------------------------------------------------------
>
> Key: FELIX-6103
> URL: https://issues.apache.org/jira/browse/FELIX-6103
> Project: Felix
> Issue Type: Bug
> Components: File Install
> Reporter: Mariano Alvaro
> Assignee: Raymond Augé
> Priority: Major
> Fix For: fileinstall-3.6.6
>
> Attachments: diffs.txt
>
>
> When using a NotCachablePersistenceManager the following steps occur when
> changing .config file values:
>
> # ConfigInstaller.setConfig gets called.
> # Configuration gets retrieved from ConfigInstaller.getConfiguration method
> # getConfigurationAdmin().listConfigurations(filter) returns a new
> configuration each time because NotCacheablePersitenceManger is used.
> # Changes are performed in the new Configuration.
> # ConfigInstaller.doConfigurationEvent gets called back and retrieves
> configuration from configurationAdmin.
> # ConfigurationAdmin.getConfiguration retrieves cached value (hasn't been
> updated in step 4 because a new differente configuration was returned)
> # config file gets updated with cached values
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
