You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/09/21 16:20:16 UTC

[jira] Reopened: (SLING-1112) ValueMap doesn't allow "deep property fetching" anymore

     [ https://issues.apache.org/jira/browse/SLING-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler reopened SLING-1112:
-------------------------------------

      Assignee: Carsten Ziegeler

Reopening this bug after rethinking the whole thing - it seems more convenient to support getting deep properties than preventing this.


> ValueMap doesn't allow "deep property fetching" anymore
> -------------------------------------------------------
>
>                 Key: SLING-1112
>                 URL: https://issues.apache.org/jira/browse/SLING-1112
>             Project: Sling
>          Issue Type: Bug
>          Components: JCR
>    Affects Versions: JCR Resource 2.0.6
>         Environment: Day CQ5.2.1
>            Reporter: zhangchunlong
>            Assignee: Carsten Ziegeler
>         Attachments: DeepResolvingValueMap.java
>
>
> ValueMap doesn't allow "deep property fetching" anymore --> Breaks our code
> In our code we use heavily deep property fetching:
> Example 1:
> final ValueMap properties = ResourceUtil.getValueMap(this.resource);
> properties.get("categories_c1/categories", String[].class);
> Example 2:
> final ValueMap map = ResourceUtil.getValueMap(resource);
> final String propertyValue = map.get("language_config/print", String.class);
> the resource points to a page which has a component (e.g. "language_config").
> Using the "/" we fetch the nested property of the component (like a qualident),
> This worked fine before, now always "null" is returned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.