You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Alexander Falb (JIRA)" <ji...@apache.org> on 2017/07/10 13:29:00 UTC
[jira] [Commented] (DELTASPIKE-1277) Force refresh of cached config
values
[ https://issues.apache.org/jira/browse/DELTASPIKE-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080324#comment-16080324 ]
Alexander Falb commented on DELTASPIKE-1277:
--------------------------------------------
Hi Romain,
I'm not sure about which storage by application you are talking about. The {{Map<ClassLoader, ConfigSource[]> configSources}}?
Having a service (Bean or just some static methods) to retrieve all PropertyBuilders created by the application would be the goal. Ofc an iterator of them would provide even more options than a simple {{getByKey}}, like the proposed {{refreshValue("key")}}. But I'm still not sure where to collect all the created PropertyBuilders.
Alex
> Force refresh of cached config values
> -------------------------------------
>
> Key: DELTASPIKE-1277
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1277
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Configuration
> Reporter: Alexander Falb
> Attachments: forcerefresh.patch
>
>
> When using a {{TypedResolver}} or {{UntypedResolver}} with caching enabled, there is no way of bypassing the cache and forcefully reloading the value from underlying datasources.
> The attached patch is a proposal of creating such an mechanism. It introduces a {{void forceRefresh()}} method to the {{TypedResolver}}, implements this method by resetting the {{reloadAfter}} field and adds a unit test.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)