DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35529>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35529 Summary: FileChangedReloadingStrategy javadoc misleading Product: Commons Version: unspecified Platform: Sun URL: http://jakarta.apache.org/commons/configuration/apidocs/ org/apache/commons/configuration/reloading/FileChangedRe loadingStrategy.html OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Configuration AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] The current javadoc for 1.1 version of Configuration is as follows: ----- A reloading strategy that will reload the configuration every time its underlying file is changed. The file is not reloaded more than once every 5 seconds by default, this time can be changed by setting the refresh delay. This strategy only works with FileConfiguration instances. ----- I was under the false impression that a thread would be created which would periodically wake up every 5 seconds and poll the property file to see if it has changed or not. If the file has changed then it would be reloaded. However this is not the case. After diving into the code, you need to call one of the get*() methods (i.e. getInt(), getLong(), etc...) before the file is checked. Finally, it would be nice to have some kind of callback mechanism to notify listeners that implement a well known interface defined in the configuration API that the file has changed. Thanks for all your hard work! -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
