You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Nicolas Peltier (JIRA)" <ji...@apache.org> on 2018/04/24 13:31:01 UTC
[jira] [Closed] (SLING-7241) [pipes] Nashorn ScriptEngine in
PipeBindings is null
[ https://issues.apache.org/jira/browse/SLING-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Peltier closed SLING-7241.
----------------------------------
> [pipes] Nashorn ScriptEngine in PipeBindings is null
> ----------------------------------------------------
>
> Key: SLING-7241
> URL: https://issues.apache.org/jira/browse/SLING-7241
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Pipes 1.0.4
> Environment: java.runtime.name = Java(TM) SE Runtime Environment
> java.runtime.version = 1.8.0_144-b01
> Reporter: Björn Csott
> Assignee: Nicolas Peltier
> Priority: Minor
> Fix For: pipes 2.0.2
>
> Attachments: error.log
>
>
> Under some unclear circumstances the ScriptEngine in PipeBindings does not get initialized.
> There is a solution out there to attach Nashorn to the system bundle. Appart from that I was able to fix it by using a different constructor: ScriptEngineManager(null).
> The issue can be reproduced by deploying https://github.com/bcsott/migration-tool
> When it fails the following is written to stderror.log:
> ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory:
> Provider jdk.nashorn.api.scripting.NashornScriptEngineFactory not found
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)