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 2019/12/06 12:04:00 UTC

[jira] [Updated] (SLING-8892) Unwrap LazyBindings.Supplier values in the RhinoJavaScriptEngine

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

Radu Cotescu updated SLING-8892:
--------------------------------
    Description: Starting with SLING-8737, {{BindingsValuesProviders}} can now take advantage of {{LazyBindings}} and provide values through {{LazyBindings.Supplier}} instances. The {{RhinoJavaScriptEngine}} should correctly unwrap these values when defining the scope for a JavaScript script.  (was: Starting with SLING-8737, {{BindingsValuesProviders}} can now take advantage of {{LazyBindings}} and provide values through {{LazyBindings.Supplier}}s. The {{RhinoJavaScriptEngine}} should correctly unwrap these values when defining the scope for a JavaScript script.)

> Unwrap LazyBindings.Supplier values in the RhinoJavaScriptEngine
> ----------------------------------------------------------------
>
>                 Key: SLING-8892
>                 URL: https://issues.apache.org/jira/browse/SLING-8892
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting JavaScript 3.1.2
>
>
> Starting with SLING-8737, {{BindingsValuesProviders}} can now take advantage of {{LazyBindings}} and provide values through {{LazyBindings.Supplier}} instances. The {{RhinoJavaScriptEngine}} should correctly unwrap these values when defining the scope for a JavaScript script.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)