commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-228) XMLConfiguration.subset() with FileChangedReloadingStrategy does *not* 'see' file changes
Date Fri, 22 Sep 2006 17:33:23 GMT
Oliver Heger commented on CONFIGURATION-228:

I think the problem here is that the subset configuration returned by XMLConfiguration is
not life, i.e. it is not really connected to the parent configuration. There was a bug report
(CONFIGURATION-212) describing this problem.

In the current code base there is the new method configurationAt(String key) in HierarichicalConfiguration
that returns a life configuration. You can try this method as an alternative.

But maybe the subset() implementation should be changed to return a life subset, too.

> XMLConfiguration.subset() with FileChangedReloadingStrategy does *not* 'see' file changes
> -----------------------------------------------------------------------------------------
>                 Key: CONFIGURATION-228
>                 URL:
>             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:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message