[ 
http://issues.apache.org/jira/browse/CONFIGURATION-228?page=comments#action_12437659
 ] 
            
Oliver Heger commented on CONFIGURATION-228:
--------------------------------------------

Sounds plausible. I will have a look.

Is there any chance that you can provide a junit test? If not, that's no 
problem; I think the issue should not be too difficult to reproduce.

> XMLConfiguration.subset() with FileChangedReloadingStrategy does *not* 'see' 
> file changes
> -----------------------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-228
>                 URL: http://issues.apache.org/jira/browse/CONFIGURATION-228
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.2 Final
>            Reporter: Janusz Studzizba
>
> XMLConfiguration.subset() with FileChangedReloadingStrategy does *not* 'see' 
> file changes
> Configuration.xml:
> <conf>
>     <parent-item>
>         <sub-item>old_value</sub-item>
>     </parent-item>
> </conf>
> 1. XMLConfiguration is loaded:
>             config = new XMLConfiguration("c:\\conf.xml");
>             config.setReloadingStrategy(new FileChangedReloadingStrategy());
> 2. Now, <sub-item> node value changes to "new_value",
> and the code:
>             Configuration parentItemConfig = config.subset("parent-item"); 
> [AA]
>             String ss2 = parentItemConfig.getString("sub-item");
> returns "old_value" !!!
> while:  config.getString("parent-item.sub-item"); returns new refreshed value.
> It is a bug, we have FileChangedReloadingStrategy, we create new subset in 
> [AA] but receive old values.
> [for now, workaround for config users is to call config.reload() when 
> strategy.hasChanged()]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to