[
https://issues.apache.org/jira/browse/SLING-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369283#comment-14369283
]
ASF GitHub Bot commented on SLING-4524:
---------------------------------------
GitHub user olaf-otto opened a pull request:
https://github.com/apache/sling/pull/74
SLING-4524: Provide the properties of the current Resource as a ValueMap...
https://issues.apache.org/jira/browse/SLING-4524: Provide the properties of
the current Resource as a ValueMap via the sling:defineObjects tag
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olaf-otto/sling feature/SLING-4524
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/74.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #74
----
commit 2bf94d8ab5bef2344ec4ac346a07c5444fdb3fec
Author: olaf-otto <[email protected]>
Date: 2015-03-19T12:53:08Z
SLING-4524: Provide the properties of the current Resource as a ValueMap
via the sling:defineObjects tag
----
> Provide the properties of the current Resource as a ValueMap via the
> sling:defineObjects tag
> --------------------------------------------------------------------------------------------
>
> Key: SLING-4524
> URL: https://issues.apache.org/jira/browse/SLING-4524
> Project: Sling
> Issue Type: Wish
> Reporter: Olaf Otto
>
> One of the most common use cases in JSP views is accessing the properties of
> the current resource. However, this currently requires explicit adaptation of
> the current resource to ValueMap, which is boilerplate. I'd thus love to see
> "properties" as one of the defaults provided by the before mentioned tag
> library.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
