You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2016/03/24 21:13:26 UTC

[jira] [Updated] (CONFIGURATION-288) getConfigurationNames() does not report names of nested configurations

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

Oliver Heger updated CONFIGURATION-288:
---------------------------------------
    Fix Version/s:     (was: 2.0)
                   2.x

> getConfigurationNames() does not report names of nested configurations
> ----------------------------------------------------------------------
>
>                 Key: CONFIGURATION-288
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-288
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.4
>         Environment: using trunk of august 6 2007
>            Reporter: Thorbjørn Ravn Andersen
>            Priority: Minor
>             Fix For: 2.x
>
>         Attachments: A.xml, B.xml, C.properties, GetNestedConfigurationName.java, namedConfiguration.jar
>
>
> Given a <configuration> A which includes a <configuration> B which in turn loads the <properties> C.
> A and C has the config-name attribute.  B does not.
> Calling A.getConfigurationNames() does not return the name of C.  From my initial reading of the code, it only returns names on the B level.
> It also appears that the name for A does not appear either.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)