You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/07/13 14:51:01 UTC
[jira] [Closed] (SLING-9255) Allow servlet resolution based on path
[ https://issues.apache.org/jira/browse/SLING-9255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu closed SLING-9255.
-------------------------------
> Allow servlet resolution based on path
> --------------------------------------
>
> Key: SLING-9255
> URL: https://issues.apache.org/jira/browse/SLING-9255
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Servlets Resolver 2.7.0
>
>
> In Sling, scripts can include other scripts at runtime through several script engine specific implementations (e.g. {{data-sly-include}}, {{sling:call}}, etc.). All of the implementations rely on the {{org.apache.sling.api.servlets.ServletResolver#resolveServlet(org.apache.sling.api.resource.Resource, java.lang.String)}} method to resolve the script.
> With bundled scripts, the scripts are not any more part of the resource tree. However, the Sling Scripting Bundle Tracker could use the path-based servlet registration mechanism to place the servlet wrapping the script / precompiled unit at the same path as the caller expected the script to be present in the resource tree.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)