You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2008/02/06 16:49:08 UTC
[jira] Commented: (SLING-227) sling:include tag: use
ResourceResolver.resolve(String) method to get the resource
[ https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566162#action_12566162 ]
Tobias Bocanegra commented on SLING-227:
----------------------------------------
the latest fix produces endless loops when including <sling:include path="foobar"/>
in this case the script of 'this' resource is included.
> 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.