[
https://issues.apache.org/jira/browse/SLING-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-6166.
---------------------------------
Resolution: Fixed
> Update the HTL bundles to use the SLING-6165 request-scoped resource resolver
> -----------------------------------------------------------------------------
>
> Key: SLING-6166
> URL: https://issues.apache.org/jira/browse/SLING-6166
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting HTL JS Use Provider 1.0.16, Scripting HTL
> Engine 1.0.26
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Fix For: Scripting HTL JS Use Provider 1.0.18, Scripting HTL
> Engine 1.0.28
>
>
> The fix for SLING-6156 brings in a performance penalty for the JS Use
> Provider since a resource resolver is needed every time when dependency
> resolution is performed. When SLING-6165 is implemented, the JS Use Provider
> should switch to this new API.
> Additionally, the HTL Scripting Engine should also switch to the same
> resolver for script resolution, instead of relying on the admin resolver
> passed through the {{ScriptContext}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
