[ https://issues.apache.org/jira/browse/SLING-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265124#comment-16265124 ]
Bertrand Delacretaz commented on SLING-7241: -------------------------------------------- IIUC there's a classloader related reason for calling {{ScriptEngineManager(null).getEngineByName("nashorn")}} twice? If that's correct please add comments to explain the idea - right now I'd say one of those calls should go away but it looks like there's a specific reason for doing that. Also, "nashorn" should be a constant I guess ;-) > [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.0 > > 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)