Automatic reload for configuration files. about owner HOT 3 CLOSED

Started working on branch "automatic-reload" 9056c8b

The idea is to have an annotation like @hotreload(checkInterval) on class level, example:

@HotReload(5L, TimeUnit.MINUTES)
interface MyConfig extends Config {...}

Something like this would happen:

PropertyInvokationHandler.invoke() -> PropertyLoader.ensureUpToDate() -> LoadPolicy.checkAndUpdate()

With proper thread synchronization.

from owner.

Basic reload is implemented.

The problem is that if the configuration is invalid (example, a non-numeric value for a method returning a numeric value) will generate an exception when the method is invoked, a runtime exception.

So, it would be best to have the validation feature, so that when reload is triggered the validation ensures that the new configuration is valid before to adopt it; and if it's not valid then the new configuration is discarded with some log message somewhere.

At the moment the reload happens synchronously (when a method on the proxy is invoked), but it would be nice if the user could chose also an asynchronous reload (by a thread in background) with a notification mechanism based on listeners.

Things to be done before completing this issue:

• more tests
• validation #30
• documentation
• asynchronous reload
• notifications (ReloadEvent, ReloadListener)

from owner.

Documentation written to http://owner.aeonbits.org/docs/reload/

The validation will be postponed after 1.0.4 release probably. Hot reload can also live without validation for the moment.

from owner.