Using Nashorn Script Engine in AEM

[Nitin_Tyagi]

Hi All,

I am currently working on  AEM SP2 with JDK8 & trying to build a Handlebar Script Engine in AEM. For the Handlebar Compilation & processing we were loading the Nashorn Script Engine inside AEM & the Nashorn will be used to evaluate handlebars.js & other processing. I am loading the Nashorn engine as per instructions on http://www.oracle.com/technetwork/articles/java/jf14-nashorn-2126515.html with below lines of code. But the nashorn Engine is not initializing.

ScriptEngineManager engineManager = new ScriptEngineManager(); ScriptEngine engine = engineManager.getEngineByName("nashorn");

Another option which I tries was to Initialize  ScriptEngineManager via OSGi @Reference Notation. When I do that It gives me all the Registered Script Engines in AEM available @ http://localhost:4502/system/console/status-slingscripting , but again Nashorn isn't among them.

Can anyone help me how to load Nashorn Engine inside AEM or do I have to do a Custom Implementation OF Nashorn Script Engine in AEM?

Thanks

Nitin

[Peter_Puzanovs]

Hey Nitin,

Current AEM6 runtime is Rhino and it's implementation can be found here:

org.apache.sling.scripting.javascript.RhinoJavaScriptEngine

As per my current understanding Nashorn is not supported in AEM 6, even so it's added as default engine in JDK 8.

Peter

[justin_at_adobe · Accepted solution]

From within AEM, the available ScriptEngineManager does not pick up ScriptEngines (like Nashorn) which are registered outside the OSGi framework. You will need to register Nashorn with Sling's ScriptEngineManager. Better yet would be if Nashorn was available as an OSGi bundle, in which case it could just be dropped in. This is the case, for example, with Groovy.

[Nitin_Tyagi]

Thanks for your response Peter. Yes It's not yet added in the AEM's list of Script Engines. That's the reason I am trying to load it directly from JDK considering nashorn.jar is already in the classpath.

ScriptEngineManager engineManager = new ScriptEngineManager();

ScriptEngine engine = engineManager.getEngineByName("nashorn");

It looks like I will have to create a new NashornScriptEngine in AEM using nashorn.jar.

Thanks

Nitin