[
https://issues.apache.org/jira/browse/SLING-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857002#action_12857002
]
Carsten Ziegeler commented on SLING-1479:
-----------------------------------------
I've created a new version (1.1) for the new tag, so if you want to use it you
have to reference the new taglib, the old taglib (1.0) is still available for
compatiblity.
Changed in revision: 934075
> Add JSP Tag for new script resolution
> -------------------------------------
>
> Key: SLING-1479
> URL: https://issues.apache.org/jira/browse/SLING-1479
> Project: Sling
> Issue Type: New Feature
> Components: Scripting
> Affects Versions: Scripting JSP-Taglib 2.0.6
> Reporter: Felix Meschberger
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP-Taglib 2.1.0
>
>
> SLING-585 brings new Script/Servlet resolution API to find an explicitly
> named script according to a resource type hiearchy.
> This functionality should be reflected in a new JSP tag, e.g. along the lines:
> <sling:call script=... resource=... resourceType=... noResourceType=....
> />
> where:
> script is a path to a script
> resource is a resource whose resource type hierarchy is used to resolve
> the script
> resourceType is a resource type hierarchy to resolve the script
> noResourceType prevents using resource type hiearchy if set to true
> (default: false)
> If neither resource nor resource type are declared, the script is resolved
> according to the type hierarchy of the request's resource.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira