ECMAScript is our Groovy alternative

For example, the project I’m working on requires that the IT department be able to change certain business rules while the application is running. A bespoke administration interface would cost too much, and a rules engine would be too complex. Letting the user specify the rules in a Groovy might have been a good choice, but Groovy is just not ready to be used in a system that will still be maintained in ten year’s time.

Enter Javascript. It has a C-inspired syntax that Java programmers feel comfortable with, it can be loaded and re-interpreted each time the rules change, and is quite well integrated with Java. A perfect replacement for groovy in this case.

Beyond tiny, user-written scripts, Javascript has many of the features that make Groovy attractive, including latent typing and closures. Javascript also has a sophisticated, prototype-based object model that could be used to develop the kind of code that is particularly hairy in Java – marshalling and unmarshalling streams of bytes, for instance.

So it’s Javascript for the time being for us here. Hopefully, in twelve or eighteen months, Groovy will hava a solid specification and a production ready implementation, and we’ll switch.

ecmascript is much better than groovy. (FULL STOP)
but what we need is not the proliferation of hundreds of scripting languages to interact with java but a framework to gain from their sinergy.
welcome to seppia. http://www.seppia.org/

<a href="http://www.seppia.org">
Seppia is a simple framework to build and deploy any java application which combines java and javascript in unique way.
</a>