[
https://issues.apache.org/jira/browse/TAMAYA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691066#comment-16691066
]
ASF subversion and git services commented on TAMAYA-355:
--------------------------------------------------------
Commit 1fbe9a1589ecc591164d7457f0c74fdd2bb3f20a in incubator-tamaya-sandbox's
branch refs/heads/master from [~anatole]
[
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-sandbox.git;h=1fbe9a1
]
TAMAYA-355 Enable mapping of lists and arrays into internal datastructures,
reestablished conversion/filter context (backward compatible).
> Revise mapping of xml, json and yaml configurations to honor lists
> ------------------------------------------------------------------
>
> Key: TAMAYA-355
> URL: https://issues.apache.org/jira/browse/TAMAYA-355
> Project: Tamaya
> Issue Type: Improvement
> Components: Core, Extensions
> Affects Versions: 0.3-incubating
> Reporter: Anatole Tresch
> Assignee: Anatole Tresch
> Priority: Blocker
> Fix For: 0.4-incubating
>
>
> Given the following config:
> {{<config>}}
> {{ <a>}}
> {{ <b>23</b>}}
> {{ </a>}}
> {{ <a>}}
> {{ <b>15</b>}}
> {{ </a>}}
> {{</config>}}
> The current mapping (in _core_, and the _format_ related modules) results in
> a.b=15, which is invalid, because it actually looses information.
> This is basically similar for other formats. This change defines that list
> entries are mapped to arrays as follows:
> {{a[0].b=23}}
> {{a[1].b=15}}
> This syntax does not loose information and is simple enough to reestablish
> access logic such as
> {{List<Map<String,String>> as = configuration.query(ListQuery.of("a"));}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
