[
https://issues.apache.org/jira/browse/CONFIGURATION-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-333.
----------------------------------------
Resolution: Fixed
Fixed in subversion.
> Support update-aware sub-configurations for the configurationsAt() method
> -------------------------------------------------------------------------
>
> Key: CONFIGURATION-333
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-333
> Project: Commons Configuration
> Issue Type: New Feature
> Affects Versions: 1.5
> Reporter: Oliver Heger
> Assignee: Oliver Heger
> Priority: Minor
> Fix For: 2.0
>
>
> The configurationAt() method of hierarchical configurations has a
> supportsUpdates parameter. If set to true, the sub-configuration returned is
> aware of updates of its parent configuration. The configurationsAt() method
> should support a similar mechanism, too.
> Checking for updates of the parent configuration requires the
> sub-configuration to be constructed with a unique key. So far it was not
> possible to determine such a key in the configurationsAt() method because the
> key passed to this method can select multiple nodes. So a way has to be
> implemented to determine a unique key for a given configuration node.
> Having unique keys for all properties defined could be useful for other use
> cases, too. Maybe an extended version of the getKeys() method makes sense
> that returns unique keys? So each key returned by this method is guaranteed
> to map to exactly one node.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
