[
https://issues.apache.org/jira/browse/DELTASPIKE-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084084#comment-16084084
]
Romain Manni-Bucau commented on DELTASPIKE-1277:
------------------------------------------------
Hmm, not sure why it would prevent to log changes more than today. In case of
no cache we shouldnt hit any cache IMHO.
Logging a wrong value is as bad as using a wrong value at runtime because IIRC
this log statement was "ops" intended so it would lead to a misunderstanding of
the system which is quite dangerous.
What's the blocker - technically -to bypass any cache if cache is disabled?
Directly going to the ConfigResolver (configsources) sounds doable and a good
option to me. Am I missing something?
> 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: central_caching.patch, 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)
