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 2015/10/21 11:53:27 UTC

[jira] [Resolved] (SLING-5175) The current set up of the ImporterTopLevel in the RhinoJavaScriptEngine incurs performance penalties

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

Radu Cotescu resolved SLING-5175.
---------------------------------
    Resolution: Fixed

Fixed in [r1709781|https://svn.apache.org/viewvc?view=revision&revision=r1709781].

> The current set up of the ImporterTopLevel in the RhinoJavaScriptEngine incurs performance penalties
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-5175
>                 URL: https://issues.apache.org/jira/browse/SLING-5175
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting JavaScript 2.0.26
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>             Fix For: Scripting JavaScript 2.0.28
>
>
> The changes from SLING-5022, although allowed the {{importClass}} and {{importPackage}} Rhino functions to be used in JavaScript scripts, incurred performance penalties for script execution.
> The importer top level should actually be set for the {{rootScope}} provided by the {{RhinoJavaScriptEngineFactory}}.



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