commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <>
Subject [jira] Commented: (CONFIGURATION-401) HierarchicalConfiguration does not support hierarchy from property files
Date Sun, 08 Nov 2009 21:31:32 GMT


Oliver Heger commented on CONFIGURATION-401:

By converting the flat configuration to a hierarchical one a tree is constructed, but in this
case it has a different structure than you expect. It looks like the following:


The problem is that a flat configuration format like a properties file simply does not contain
enough information about the internal structure of its properties. So the algorithm that creates
a hierarchical configuration from this data has no information how it should combine certain
properties (e.g. add multiple _person_ elements instead of adding all data to a single _person_

I don't think there is much we can do about this. An algorithm smart enough to deal with this
problem would really be complex - if it is feasable at all.

> HierarchicalConfiguration does not support hierarchy  from property files
> -------------------------------------------------------------------------
>                 Key: CONFIGURATION-401
>                 URL:
>             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.surName=2
> persons.person.phoneNum=3
> persons.person.surName=5
> persons.person.phoneNum=6
> 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.

View raw message