You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Mariano Alvaro (JIRA)" <ji...@apache.org> on 2019/04/16 16:13:01 UTC
[jira] [Commented] (FELIX-6103) ConfigInstaller, when using
NotCachablePersistenceManager, can restore cached stale properties
[ https://issues.apache.org/jira/browse/FELIX-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819199#comment-16819199 ]
Mariano Alvaro commented on FELIX-6103:
---------------------------------------
Possible solution attached: [^diffs.txt]
> 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
> Reporter: Mariano Alvaro
> Priority: Major
> 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
(v7.6.3#76005)