sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Peltier (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7241) [pipes] Nashorn ScriptEngine in PipeBindings is null
Date Thu, 16 Nov 2017 10:44:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255107#comment-16255107
] 

Nicolas Peltier commented on SLING-7241:
----------------------------------------

[~karlpauls] that's not noise, it's fine enriching this ticket with your lights. 

[~bcsott] i'm fine merging in your change, but with some comment explaining that parameter
as said (pls amend your commit and push --force so you have only one commit)
thanks!

> [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
>            Priority: Minor
>         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
(v6.4.14#64029)

Mime
View raw message