By default the java compiler will only pick up classpath that the JVM itself was started with.
For scenarios where the usage of java-scriptengine is directly utilized within a "main" program or similar this is sufficient.
But in scenarios where the usage of java-scriptengine is utilized within a java servlet container (deployed as a war or similar) then the classpath picked up by the java compiler does not contain the contents of the servlet application.
In such scenarios it is required that options are passed to the java compiler to include -classpath (Java 9+ -modulepath as well) to be able to compile scripts within the container without issue.
Getting into what the compilation options should be is application specific, so the easiest solution is to simply accept and pass options through.
By default the java compiler will only pick up classpath that the JVM itself was started with.
For scenarios where the usage of java-scriptengine is directly utilized within a "main" program or similar this is sufficient.
But in scenarios where the usage of java-scriptengine is utilized within a java servlet container (deployed as a war or similar) then the classpath picked up by the java compiler does not contain the contents of the servlet application.
In such scenarios it is required that options are passed to the java compiler to include
-classpath(Java 9+-modulepathas well) to be able to compile scripts within the container without issue.Getting into what the compilation options should be is application specific, so the easiest solution is to simply accept and pass options through.