[
https://issues.apache.org/jira/browse/SLING-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605346#comment-13605346
]
Carsten Ziegeler commented on SLING-2790:
-----------------------------------------
That doesn't convince me :) It seems that this is a common use case and hiding
the information in request attributes is not really user friendly - especially
as request attributes do not provide any type safety
> Need a way to get the resource of the original request in a subcomponent
> ------------------------------------------------------------------------
>
> Key: SLING-2790
> URL: https://issues.apache.org/jira/browse/SLING-2790
> Project: Sling
> Issue Type: Improvement
> Components: API
> Reporter: Axel Hanikel
> Priority: Minor
>
> - I have created a component at
> /apps/training/components/tasklist/tasklist.jsp.
> - I have a page node at /content/training with a sling:resourceType of
> training/components/page
> - That page has a subnode /content/training/content/tasklist with a
> sling:resourceType of training/components/tasklist (the tasklist.jsp from
> above)
> In the tasklist.jsp, I would like to get the path to the resource of the
> original HTTP request, i.e. /content/training. I expected to get it using
> slingRequest.getRequestPathInfo().getResourcePath() but that gets me the path
> to the current resource (/content/training/content/tasklist), not the path to
> the request.
> Having the original resource in a predefined variable or a call like
> slingRequest.getOriginalRequestPathInfo() would be very helpful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
