[
https://issues.apache.org/jira/browse/LOGCXX-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966462#comment-13966462
]
Thorsten Schöning commented on LOGCXX-429:
------------------------------------------
There's additional aspects to consider: If we decide to provide a callback to
execute code after the configuration file has been reloaded, we should as well
provide one to execute code before the file gets updated. Reason is that one
user changes the content of a configuration file to e.g. remove loggers from it
and those removed loggers only take effect if the logger repo has been cleared
or the global configuration state reinitialized. This could be easily done
using a callback before the file configuration gets reloaded.
http://mail-archives.apache.org/mod_mbox/logging-log4cxx-user/201404.mbox/%[email protected]%3e
http://mail-archives.apache.org/mod_mbox/logging-log4cxx-user/201404.mbox/%[email protected]%3e
> Filewatcher configuration updated callback.
> -------------------------------------------
>
> Key: LOGCXX-429
> URL: https://issues.apache.org/jira/browse/LOGCXX-429
> Project: Log4cxx
> Issue Type: Improvement
> Components: Configurator
> Reporter: Joseph Southwell
> Priority: Minor
>
> We have a user who wants to partially configure from a file and needs a way
> to update the configuration with his changes any time the file watcher thread
> reloads the configuration file. After discussing this on the list the
> consensus seems to be that we could have a callback the FileWatcher calls
> whenever it updates the configuration.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
