You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "irina fridkina (JIRA)" <ji...@apache.org> on 2007/08/13 23:37:30 UTC
[jira] Issue Comment Edited: (CONFIGURATION-292) removeChild()
doen't trigger auto saving
[ https://issues.apache.org/jira/browse/CONFIGURATION-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519531 ]
ifridkina edited comment on CONFIGURATION-292 at 8/13/07 2:35 PM:
-----------------------------------------------------------------------
What if I want to remove a specific child element rather then all children with the given name. Why not make removeNode(ConfigurationNode node) public and add a remove node event?
was (Author: ifridkina):
What if I want to remove a specific node rather then all children with the given name. Why not make removeNode(ConfigurationNode node) public and add a remove node event?
> 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.