[
https://issues.apache.org/jira/browse/CONFIGURATION-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-575.
----------------------------------------
Resolution: Fixed
Fixed after the integration of the immutableNodes branch in revision 1588831.
> Use immutable node structures in hierarchical configurations
> ------------------------------------------------------------
>
> Key: CONFIGURATION-575
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-575
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.9
> Reporter: Oliver Heger
> Fix For: 2.0
>
>
> Currently, hierarchical configurations use {{ConfigurationNode}} objects to
> represent their hierarchical node structures. These objects are mutable;
> there are set methods for altering node names, values, children, attributes,
> and more. This is problematic for various reasons:
> * Client code can alter the structure directly circumventing mechanisms of
> the configuration object.
> * In a multi-threaded environment all accesses have to be synchronized
> because one cannot be sure when an underlying structure is modified.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
