Switch from Nashorn to GraalVM for javascript execution

[jeremythuff]

1. Add the GraalVM JavaScript JAR to your classpath. If you're using Maven, you can add this dependency to your pom.xml:

<dependency>
    <groupId>org.graalvm.js</groupId>
    <artifactId>js</artifactId>
    <version>19.3.1</version>
</dependency>

2. Configure Camunda to use GraalVM JavaScript. You can do this by setting the javascriptScriptEngine property in your bpm-platform.xml, processes.xml or camunda.cfg.xml:

<property name="javascriptScriptEngine">graal.js</property>

Remember to replace the version number with the version of GraalVM JavaScript that you're using.

Please note that while GraalVM JavaScript is largely compatible with Nashorn, there might be some differences in behavior. You should thoroughly test your scripts after switching to GraalVM JavaScript to make sure they still work as expected.

[kaladay]

Java 21+ has new experimental alternative to this. This is out of scope but would be worth noting when setting the version of GraalVM.

The implementation is intended to be run on numerous languages, however, our priority is Javascript. Test using Ruby and other languages if possible. If it fails in languages other than Javascript, then report this as a regression.

This is the Foreign Function & Memory API. By Java 21+ this is third preview and is probably close to being stable but is also not yet stable.

...the API enables Java programs to call native libraries and process native data without the brittleness and danger of JNI...

see: https://openjdk.org/jeps/442

[kaladay]

The minimum required Java version is Java 17.

[kaladay]

This issue should be in mod-camunda and not fw-registry.
The PR for this issue is: TAMULib/mod-camunda#221