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 2016/11/25 15:43:58 UTC

[jira] [Updated] (SLING-6166) Update the HTL bundles to use the SLING-6165 request-scoped resource resolver

     [ https://issues.apache.org/jira/browse/SLING-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radu Cotescu updated SLING-6166:
--------------------------------
    Summary: Update the HTL bundles to use the SLING-6165 request-scoped resource resolver  (was: Update the JS Use Provider to use the SLING-6165 request-scoped resource resolver)

> 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
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>             Fix For: Scripting HTL JS Use Provider 1.0.18
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)