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 2024/07/03 14:16:00 UTC
[jira] [Resolved] (SLING-11608) Cache script dependency resolution
[ https://issues.apache.org/jira/browse/SLING-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-11608.
----------------------------------
Resolution: Fixed
> Cache script dependency resolution
> ----------------------------------
>
> Key: SLING-11608
> URL: https://issues.apache.org/jira/browse/SLING-11608
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Scripting HTL Engine 1.4.22-1.4.0
>
>
> Up to version 1.4.20-1.4.0 of the HTL Script Engine, the [ScriptUtils|https://github.com/apache/sling-org-apache-sling-scripting-sightly/blob/org.apache.sling.scripting.sightly-1.4.20-1.4.0/src/main/java/org/apache/sling/scripting/sightly/impl/utils/ScriptUtils.java] class walked the resource tree to solve the correct HTL Template/script provided by another script engine based on the resource tree. However, in situations where the script tree is stable (e.g. systems that have a read-only search path, systems that deploy script exclusively via bundled scripts, etc.), it makes sense to cache this resolution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)