Details
-
Bug Report
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
Description
When creating a DMN Decision Table in Modeler (0.5.1), one can choose an alternative Language for input expressions.
One of the options is Javascript (beware the lowercase s).
When running the separate DMN (7.4.0) engine with JDK 1.8 (i.e. Nashorn scripting engine), I get the error that there is no scripting engine for "Javascript".
A little debugging shows that Nashorn is available under eight different names including "JavaScript" and "javascript" (but not "Javascript") - hence the missed match.
Changing the selected Language manually to one of the recognized names associated with Nashorn fixes the problem. I didn't test it with Rhino.
Btw. the given hint "return obj.propertyName;" produces an invalid return statement exception. The shorter "obj.propertyName;" on the other hand is evaluated like the above return statement by Nashorn.
- Please fix the typo in the JavaScript drop down option for the input expression Language.
- Consider providing a sample script that works under the default/first available script Language (JS).