[
https://issues.apache.org/jira/browse/CONFIGURATION-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger updated CONFIGURATION-292:
---------------------------------------
Fix Version/s: 2.0
Affects Version/s: (was: Nightly Builds)
1.4
When directly accessing the nodes of a hierarchical configuration you
circumvent all internal update mechanisms. For normal operations you should not
do that (why don't you call clearProperty() or clearTree() instead?). The way
hierarchical configurations are implemented at the moment makes it very hard
detect such direct changes on the raw data model.
Maybe this can be changed in a future release. We might for instance implement
an event notification mechanism that operates on a certain hierarchy of nodes.
This will however involve incompatible changes on classes and interfaces, so I
am setting the fix version to the next major release.
> removeChild() doen't trigger auto saving
> ----------------------------------------
>
> Key: CONFIGURATION-292
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-292
> Project: Commons Configuration
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: I am using Nightly build dated July 19, 2007
> Reporter: irina fridkina
> Fix For: 2.0
>
>
> When I remove nodes from the XMLConfiguration with autoSave enabled the file
> doesn't change. Here is an example
> XMLConfiguration config = new XMLConfiguration("c:\\conf.xml");
> config.setAutoSave(true) ;
> ConfigurationNode parentNode = config.getRootNode();
> parentNode.removeChild(childName);
> config.xml didn't change to reflect the changes
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
