[
https://issues.apache.org/jira/browse/CONFIGURATION-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-393.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.7
A fix was committed to both trunk and experimental branch which implements a
special treatment for collection properties.
However, as we create no general deep clone, it is possible that other mutable
Objects stored in the internal map still cause problems. Implementing a true
deep clone is probably pretty complicated and expensive. So I think the current
solution is a good compromise.
> BaseConfiguration.clone() does not work with list properties
> ------------------------------------------------------------
>
> Key: CONFIGURATION-393
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-393
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.6
> Reporter: Oliver Heger
> Assignee: Oliver Heger
> Fix For: 1.7
>
>
> In the clone() implementation the map storing the configuration data is also
> cloned. For properties with multiple values this map contains lists. Because
> no deep clone is performed these lists are simply copied into the cloned map.
> So if the corresponding properties are changed on either the original or the
> clone, the other object is affected, too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
