[
https://issues.apache.org/jira/browse/CONFIGURATION-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775023#action_12775023
]
Joerg Schaible commented on CONFIGURATION-401:
----------------------------------------------
I don't think this is a valid enhancement request. The format of the property
files are defined in the JDK as key value pairs and if you define the same key
twice, you simply override the first one. This is what you get from
Properties.load and I think we should not behave differently.
> HierarchicalConfiguration does not support hierarchy from property files
> -------------------------------------------------------------------------
>
> Key: CONFIGURATION-401
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-401
> Project: Commons Configuration
> Issue Type: Bug
> Components: Expression engine
> Affects Versions: 1.6
> Environment: windows/Linux
> Reporter: yair ogen
>
> If you have hierarchy like this:
> persons.person.name=1
> persons.person.surName=2
> persons.person.phoneNum=3
> persons.person.name=4
> persons.person.surName=5
> persons.person.phoneNum=6
> persons.person.name=7
> persons.person.surName=8
> persons.person.phoneNum=9
> If I have a regular property configuration that loaded a file containing in
> the above. then I transform into HierarchicalConfiguration using:
> ConfigurationUtils.convertToHierarchical(configuration).
> The tree is not right.
> I can do this:
> hierarchicalConfiguration.subset("persons").subset("person(0)").getKeys()
> but this returned empty iterator:
> hierarchicalConfiguration.subset("persons").subset("person(1)").getKeys()
> Only the first person is available.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
