[EMAIL PROTECTED] wrote:
Yes this is what I need - with the caveat that
when the config is reloaded, the in-memory
FileConfiguration may itself be "dirty" - meaning that
the reload should merge the changes to the
file with the changes in the in-memory FileConfiguration.
Does it work this way?
Thanks,
/U
No, the reload does not perform a merge. It just clears the
configuration and loads it again from disk. So all the changes performed
before will get lost.
I don't know an easy solution for this problem. You will probably have
to do the merging yourself. You could register a listener at the
configuration object and try to track the change events. When a reload
event occurs you have to manually apply the tracked changes again. This
approach will be problematic however if a property has changed both on
disk and in memory.
Oliver
-------------- Original message ----------------------
From: Oliver Heger <[EMAIL PROTECTED]>
[EMAIL PROTECTED] wrote:
I would like to see a simple example of PropertiesConfiguration
driven by configuration change events emitted when the underlying
file is changed.
Could you pl point me to a simple illustration?
Thanks,
/U
I am not sure whether I understand you correctly. What exactly do you
mean by "driven by configuration change events"?
Our reloading strategies do not directly fire events when a change at
the monitored file happens. The check will be performed when a property
is accessed from the associated Configuration object. If the strategy
then detects that the file was changed in the meantime, a reload is
automatically triggered for the Configuration. This will also cause the
Configuration object to fire a RELOAD event.
Is this what you need?
Oliver
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
