You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2014/03/18 12:15:04 UTC
[jira] [Commented] (SLING-585) New functionality to resolve scripts
by name
[ https://issues.apache.org/jira/browse/SLING-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939073#comment-13939073 ]
Konrad Windszus commented on SLING-585:
---------------------------------------
The original request was about including another script from within a JSP. I see that the servlet resolver was extended, but it is still not possible to use it directly from the sling:include tag. In my regard, this issue is only partly solved.
> New functionality to resolve scripts by name
> --------------------------------------------
>
> Key: SLING-585
> URL: https://issues.apache.org/jira/browse/SLING-585
> Project: Sling
> Issue Type: New Feature
> Components: API, Servlets
> Affects Versions: Servlets Resolver 2.0.8, API 2.0.8
> Reporter: Tobias Bocanegra
> Assignee: Carsten Ziegeler
> Fix For: Servlets Resolver 2.1.0, API 2.1.0
>
> Attachments: SLING585.patch
>
>
> I'm looking for a way to include a jsp script from within another but
> respecting the resource type hierarchy. so for example:
> + myapp
> + A
> + A.jsp
> + content.jsp
> + B
> - sling:resourceSuperType = "A"
> + B.jsp
> and in my B.jsp i want to include the "content.jsp" but respecting the resource type hierarchy.
> suggest to add: <slng:include scriptSelector="content" /> that internally overwrites the request selector during the script selection phase.
> see http://markmail.org/message/la4rvmcdd6whpvhl
--
This message was sent by Atlassian JIRA
(v6.2#6252)