[
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: 2.0
Priority: Minor (was: Major)
Issue Type: Improvement (was: Bug)
Affects Version/s: (was: Nightly Builds)
1.4
As I already pointed out, this is not a bug. CombinedConfiguration is designed
and works the same way as, for instance, a map does: if you put a map into
another map, its keys won't show up in the outer map either. This forms a
hierarchical name space. If you force this name space to be flat, you will
encounter problems with naming conflicts (what happens if there are sub
configurations with the same name in different CombinedConfigurations?).
That said, I nevertheless think that an easy way of accessing (sub)
configurations in a nested hierarchy is useful. I was thinking on something
like an iterator or visitor mechanism allowing to iterate over a
configuration's children. This will however probably involve some binary
incompatible changes on some interfaces, so I am setting the fix version to the
next major release.
> 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.0
>
> 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.
