[ https://issues.apache.org/jira/browse/SLING-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253239#comment-16253239 ]
Nicolas Peltier commented on SLING-7241: ---------------------------------------- thx [~bcsott] for the issue & PR! i think [~kpauls] the issue is correlated with SLING-7134, but i'm not sure it would fix it. Anyway specifying system classloader might be a good idea to avoid future headaches about why nahshorn is not here in pipes case. [~bcsott] could you add some comment explaining the choice of the engine manager (something like "we take the system classloader's engine manager to ensure consistent execution of pipes across contexts") > [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)