Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
When the GroovyScriptEngine creates a new GroovyClassLoader it always uses its classloader as the parent ClassLoader of the GroovyClassLoader. It should be possibly to specify the ClassLoader that will be used as the parent ClassLoader for new GroovyClassLoader objects when a script is run. This is necessary because a script may refer to classes/methods that don't exist on the JVM classpath. In this case, it's necessary to provide a customized URLClassLoader to allow for the script to run.