[
https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566494#action_12566494
]
Felix Meschberger commented on SLING-227:
-----------------------------------------
No, as I say in SLING-230, it is probably an error, that the resolve() methods
consider the parent path at all, because those methods are not able to decide
whether to go up the path or not on their own just based on some method names.
This is application specific and must be handled in the application.
> sling:include tag: use ResourceResolver.resolve(String) method to get the
> resource
> ----------------------------------------------------------------------------------
>
> Key: SLING-227
> URL: https://issues.apache.org/jira/browse/SLING-227
> Project: Sling
> Issue Type: Bug
> Components: JSP
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> In case of using the path attribute of the sling:include tag, the resource is
> resolved from that path using the ResourceResolver.getResource() method. If
> the path contains any selectors and/or extension, the getResource() method
> fails.
> The sling:include tag should be fixed to request a RequestDispatcher based on
> the path if the path attribute is given instead of resolving the resource
> itself, because this duplicates code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
