[
https://issues.apache.org/jira/browse/CONFIGURATION-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518128
]
Thorbjørn Ravn Andersen commented on CONFIGURATION-288:
-------------------------------------------------------
I have now created an eclipse project with a sample demonstrating what I would
like and what actually happens (can be uploaded if needed, I just uploaded the
needed files).
Seen as a new user, this "named configuration" concept is very interesting, and
I intuitively expected it to be able to get me a configuration "hidden"
somewhere in the global configuration.
My goal with this is to let commons configuration maintain reloadable
translations and log4j configuration files.
> 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
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
