commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver.He...@t-online.de (Oliver Heger)
Subject Re: [configuration]Release 1 and hierarchical configurations
Date Sat, 03 Apr 2004 14:40:35 GMT
Jörg Schaible wrote:

>Oliver Heger wrote:
>
>  
>
[snip]

>>I was thinking a bit about those hierarchical aspects and how to provide
>>access to them through the Configuration interface. My idea was to
>>introduce an interface like ConfigurationNode that describes a node in a
>>configuration tree. It could look similar to the
>>HierarchicalProperties.Node class. Then a method getRoot() could be
>>added to Configuration that returns the root node of the configuration
>>tree thus providing a tree like view on a configuration. (By the way,
>>there is already a class HierarchicalConfigurationConverter, which
>>provides means to convert a flat configuration into a hierarchical one.)
>>    
>>
>
>Just popped in my mind: What's the big difference between a Subset and a
>ConfigurationNode then ? IMHO the Subset *is* the Node for
>HierarchicalConfigurations ... 
>
>Regards,
>Jörg
>  
>
Yes, I thought of this, too. Well, a subset could also be a collection 
of  nodes, but these can be put together as children of a new root node. 
The original implementation of the subset() method in 
HierarchicalConfiguration did exactly that.

Oliver


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message