(Obviously my formatter settings in Eclipse are still suboptimal, so the resulting diff became quite large. So large that the cvs commit mail was rejected by the mailing list. Sorry about that.)
Back to the topic: The idea is that the Node objects in HierarchicalXMLConfiguration are now connected to the XML nodes they represent in the loaded document. This connection is established in the load() method. If later nodes are removed or their values are changed, these modifications are also applied to the associated XML nodes. Properties that are added to the configuration are added to the XML document before it is written.
With these enhancements HierarchicalXMLConfiguration supports now all features of XMLConfiguration plus the ability of storing properties in a hierarchical manner and keeping their structure. So I want to ask if we still need two separate XMLConfiguration classes. I suggest renaming HierarchicalXMLConfiguration to XMLConfiguration and to deprecate the original HierarchicalXMLConfiguration. In the configuration files for ConfigurationFactory the elements <xml> and <hierarchicalXML> could map to the same Configuration class (maybe the latter could log a warning that hierarchicalXML is deprecated).
If this is accepted, we can close the bugs related to XMLConfiguration messing up files on saving (31429, 32240). What do you think?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
