Brent Verner wrote:
org.apache.commons.configuration.event
ConfigurationChangedListener - receives notification when a
Configuration has changed
ConfigurationChangedEvent - sent by a ConfigurationProvider
when its Configuration (or storage) has been modified.
In my config system, I have a FileModificationMonitor
subsystem (probaby to be renamed to ResourceModificationMonitor
and contributed to a suitable jakarta project) that checks
files for modification and sends a FileModifiedEvent to
a listener.
There is a patch in Bugzilla to add support for reloadable configurations (see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25661) but no work has been done on notification yet. How far should we go for notifications ? Should we just tell the configuration has changed, or should we enumerate the modified keys ? Maybe there is a way to leverage the [event] component here.
Emmanuel Bourg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
