commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CONFIGURATION-517) Add methods to HierarchicalConfiguration to obtain sub configurations for child elements
Date Mon, 26 Nov 2012 20:54:58 GMT

     [ https://issues.apache.org/jira/browse/CONFIGURATION-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oliver Heger resolved CONFIGURATION-517.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0

Fixed in revision 1413819.
                
> Add methods to HierarchicalConfiguration to obtain sub configurations for child elements
> ----------------------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-517
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-517
>             Project: Commons Configuration
>          Issue Type: New Feature
>    Affects Versions: 1.9
>            Reporter: Oliver Heger
>             Fix For: 2.0
>
>
> So far, there is no direct way for a hierarchical configuration to obtain all elements
contained in a given section (i.e. the child elements of a specific key). This can be achieved
by operating on a {{ConfigurationNode}} object directly, but this is a low-level API, and
for further processing of the element's content it might be necessary to create a {{SubNodeConfiguration}}
around the node again.
> Therefore, it makes sense to extend the API of {{HierarchicalConfiguration}}. A method
can be added - similar to {{configurationsAt()}} - which expects a key, locates the corresponding
node, and then creates {{SubNodeConfiguration}} objects for all direct children of this node.
> It would also be useful to provide a way to query a configuration for the name of its
root element. This makes it easier to deal with dynamic configuration structures.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message