groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Ekholm <>
Subject Re: Remembering imports between script invocations
Date Thu, 08 Feb 2018 20:47:12 GMT
How do I do that via the javax.script API?

Even if this is possible via the javax.script API, chances are that a user wishes to ad-hoc
add another import, but as they are forgotten between script invocations, it makes it hard
to use Groovy to interactively create, say a Swing or JavaFX UI one line at a time. With BeanShell,
the user can add the needed imports, execute that "script" and then continue to refer to the
imported classes in the following script invocations. Making Groovy remember imports would
make it behave in as nice fashion as the new JShell tool in Java 9. JShell unfortunately cannot
run embedded via the javax.script API :-(


> On 8 Feb 2018, at 21:34, wrote:
> You can add all the imports you want to your compiler configuration and they will be
consistently available for all scripts.
> From: David Ekholm [ <>] 
> Sent: Thursday, February 08, 2018 2:12 PM
> To: <>
> Subject: Remembering imports between script invocations 
> We're considering supporting Groovy as an additional scripting language to our web gallery
software jAlbum ( <>),
but one aspect bugs me: It doesn't seem like import statements are remembered between script
invocations. This makes it far harder to use Groovy to prototype UIs within jAlbum's scripting
console than for instance BeanShell (using the javax.script API). We currently support the
slow BeanShell scripting language and JavaScript. BeanShell behaves well in this regard, remembering
earlier imported packages between script invocations. Can this be added to Groovy or is there
some API flag we can set?
> Regards
> /David, jAlbum founder and client lead developer.

View raw message