You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Emmanuel Bourg (JIRA)" <ji...@apache.org> on 2007/04/26 00:38:15 UTC

[jira] Updated: (CONFIGURATION-39) [configuration] FileChangedReloadingStrategy javadoc misleading

     [ https://issues.apache.org/jira/browse/CONFIGURATION-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bourg updated CONFIGURATION-39:
----------------------------------------

    Fix Version/s: 1.2

> [configuration] FileChangedReloadingStrategy javadoc misleading
> ---------------------------------------------------------------
>
>                 Key: CONFIGURATION-39
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-39
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.1
>         Environment: Operating System: All
> Platform: All
>            Reporter: John Nikolai
>            Priority: Trivial
>             Fix For: 1.2
>
>
> 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!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org