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

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

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

Carsten Ziegeler resolved SLING-1112.
-------------------------------------

    Resolution: Won't Fix

Actually the former behaviour was a bug - it is not expected to return values of a child node through the value map. The contract of the value
map is to return the properties of the current resource (flat).
Starting with 2.0.6 we encode properties if they contain illegal characters (for jcr prop names) - therefore a slash now gets correctly encoded.

Is this was actually a bug, I'll close this as wontfix

> 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: API
>    Affects Versions: API 2.0.6
>         Environment: Day CQ5.2.1
>            Reporter: zhangchunlong
>             Fix For: API 2.0.6
>
>
> 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.