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

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

    [ https://issues.apache.org/jira/browse/SLING-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756325#action_12756325 ] 

zhangchunlong commented on SLING-1112:
--------------------------------------

This wasn't documented in the API before and our customer had make use of a lot of these ValueMap deep referencing in their codes.
It is quite hard to build a system when the framework below changes its method behavior on each minor version. At the same time, I think many other customers might have the same problem.

Can Sling not provide a method called "getDeep", so that we can migrate without huge efforts? thanks.


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