Groovy 2.0 has been released. It's main feature is the ability to statically compile methods/classes. So you gain the benefits of static typing, without loosing the abilities of a dynamic language.
This Session will covers the following topics:
I’ve recently needed to support creating a Groovy DSL that can be called from Java, to allow scripting of some server activities. The aim was to load a file, script.groovy, and run it so that it uses the server’s API.
Researching the subject, most articles discuss how to create nicer looking syntax when working from within Groovy. Things like being able to write 5.euro. But in our scenario there were other goals:
I need a recommendation on "light" in-memory database for small groovy web-application.
The blog post compares the performance of quicksort implemented in Java, Scala, Groovy and Groovy++.
(Groovy++ is an effort to create a statically typed variant of Groovy, so that dynamic and static programming can be mixed).
In one of my previous projects I was asked to setup the environment / automate integration tests (Referred to as Itest from now on) which required a machine with 2 CPU's & 5 GB RAM, this means that in any case a developer wishing to run Itests will never be able to run them locally, and will have to use some existing server.
Maven 3 will have extensive support for Groovy:
- It will be possible for the pom file itself to be written in Groovy. This means the pom can be created with dynamic code.
- Executing Groovy code directly at different lifecycle points
- Short syntax for defining dependencies
The pom files will be translated to XML, so tool support (IDE integration) will continue to work.
Vivek Pandey, GlassFish technical lead for scripting languages support, and Jacob Kessler, GlassFish scripting engineer and self-described code monkey, presented Dynamic Languages Powered by GlassFish v3 Application Server (TS 4921) on Wednesday at the JavaOne conference.