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 2007/08/06 22:07:59 UTC
[jira] Commented: (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:comment-tabpanel#action_12518005 ]
Oliver Heger commented on CONFIGURATION-288:
--------------------------------------------
Could you please provide an example configuration file and a short code fragment, so this issue can be easier reproduced? Thanks.
>From your description I am not convinced that this is a bug. It was intended that only the names of configurations directly added to a combined configuration are returned by getConfigurationNames(). A combined configuration is not aware of any nested combined configurations.
> 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: Bug
> Affects Versions: Nightly Builds
> Environment: using trunk of august 6 2007
> Reporter: Thorbjørn Ravn Andersen
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.