Why does ReloadableResourceBundleMessageSource's
setCacheSeconds comments say don't use in production?
And what is the standard way in Spring to refresh properties or beans in an application context on a schedule:
-Call refresh() on the configurableapplicationcontext via a schedule or
"3.14. Setting a bean property as the result of a method invocation"
-Extending an application context with a timer?
I've been looking for THE way to refresh config data periodically in Spring, i.e. the conventional way might be to write a TimerTask to read the property file...