[
https://issues.apache.org/jira/browse/SLING-9255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-9255.
---------------------------------
Resolution: Fixed
Fixed in [commit
2aba608|https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker/commit/2aba608].
> 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: Scripting Bundle Tracker 0.2.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)
