You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/03/26 16:50:11 UTC

[jira] Resolved: (SLING-898) Sling JSP Include tag does not take resource super types into account for synthetic resources

     [ https://issues.apache.org/jira/browse/SLING-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-898.
-------------------------------------

    Resolution: Fixed

Added a DispatcherSyntheticResource overwriting the getResourceSuperType() method using the JcrResourceUtil.getResourceSuperType method to try resolve the resource super type in Rev. 758695.

> Sling JSP Include tag does not take resource super types into account for synthetic resources
> ---------------------------------------------------------------------------------------------
>
>                 Key: SLING-898
>                 URL: https://issues.apache.org/jira/browse/SLING-898
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting JSP
>    Affects Versions: Scripting JSP-Taglib 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Scripting JSP-Taglib 2.0.4
>
>
> Consider a repository structure like this
>    /apps/type/base/GET.jsp
>    /apps/type/extended/sling:resourceSuperType = type/base
> Now including a resource "/content/missing" like
>     <sling:include path="/content/missing" resourceType="type/extended" />
> is expected to call the GET.jsp script for a GET request.
> This does not work, since the SyntheticResource created by the include tag implementation always returns null for the resource super type.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.