It is surely possible to fix this and there are already some patches addressing some of those issues, but I ask myself do we need a flat representation of XML configuration files at all? HierarchicalXMLConfiguration already has the functionality of storing XML files in a hierarchical manner, so no structure is lost. The patches for XMLConfiguration implement functionality that HierarchicalXMLConfiguration already has. As it comes out XMLConfiguration will become a kind of HierarchicalXMLConfiguration (using DOM to store hierarchical structure) with an additional map for accessing properties.
How about removing XMLConfiguration and renaming HierarchicalXMLConfiguration to XMLConfiguration? This class still needs load() and save() methods to be compatible with the other configuration classes, but then it fully supports working with XML files.
Just a suggetion. Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
