[
https://issues.apache.org/jira/browse/SLING-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756397#action_12756397
]
Felix Meschberger commented on SLING-1112:
------------------------------------------
I think the JavaDoc is relatively clear:
The <code>ValueMap</code> is an easy way to access properties of a resource.
With most resources you can use {...@link Resource#adaptTo(Class)} to adapt
the
resource to a value map. The various getter methods can be used to get the
properties of the resource.
There is no notion of child resource/node properties being supported. Only
about properties of a resource. Sorry, this is not an API change. You really
only depended on an implementation bug....
> 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.
