Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <764537140.1257881128240.JavaMail.jira@brutus>
Date: Tue, 10 Nov 2009 19:25:28 +0000 (UTC)
From: "Oliver Heger (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Commented: (CONFIGURATION-401) HierarchicalConfiguration
 does not support hierarchy  from property files
In-Reply-To: <1676176538.1257691952515.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CONFIGURATION-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776026#action_12776026 ] 

Oliver Heger commented on CONFIGURATION-401:
--------------------------------------------

In your special example the {{PropertiesConfiguration}} contains 3 keys: _persons.person.name_, _persons.person.surName_, and _persons.person.phoneNum_. Each key is associated with a list of values. In this concrete case it is possible to convert this data into a hierarchical structure.

But as soon as the structure becomes slightly more complex, you are lost. Consider the example where persons are organized in groups, and you have properties like

{code}
persons.group.name=admins
persons.person.name=x
persons.person.name=y

persons.group.name=users
persons.person.name=z
{code}

Here you have two groups and three persons, but after the properties are read into a {{PropertiesConfiguration}} how do you know which persons belong to which group?

You try to extract structure from a format that is simply not provided.

> 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.