[
https://issues.apache.org/jira/browse/SLING-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-227.
-----------------------------------
Resolution: Fixed
Do not actually use the resolved resource just use it to test whether a
SyntheticResource must be created or not. Finally retrieve the
RequestDispatcher with the resource or the path depending on what is available.
Fixed in Rev. 618997
> 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.
