No. That's what one of the limitations we fight against in JSR-223. It is very limited, and doesn't support any kind of configuration of the engine. In other words, if you don't need to rely on the limited JSR-223 api, better use the Groovy specific engine instead.
2015-07-20 13:54 GMT+02:00 Steve Amerige <steve.amer...@sas.com>: > I received the question: > > *org.codehaus.groovy *implementation of Groovy (groovy-all) provides a > mechanism to set imports when evaluating Groovy code via * > CompilerConfiguration *and *ImportCustomizer*. I don't see the equivalent > in *javax.script *in *ScriptEngine*/*ScriptContext*. Is there a way I can > add (implicit) imports in *javax.script*, perhaps by setting a *ScriptContext > *attribute? > > > Can anyone throw any light on this? MrHaki has a nice article > <http://mrhaki.blogspot.com/2011/06/groovy-goodness-add-imports.html?_sm_au_=iVV4skZWKl7N5q75> > on the Groovy side. > > Thanks, > Steve Amerige > Principal Software Developer, Fraud and Compliance Solutions Development > SAS Institute, 100 SAS Campus Dr, Room U3050, Cary, NC 27513-8617 > > > > >
