Oracle backs Groovy and Grails

Around JavaOne 06, Oracle made a significant announcement which perhaps because of the hype around Ajax and EJB 3.0, was missed by many Java developers.
Oracle announced its plan to support Groovy and Grails and the new JSR-223 specification to enable scripting languages. Groovy is an agile dynamic language for the Java Platform while Grails is an open-source web application framework that uses Groovy to bring Ruby On Rails ideas to the java world.

Although scripting languages have been a topic for discussion for some time now, none of the major Java players had invested much time, money and effort in pushing these languages. With this announcement, Oracle has got behind Groovy and Grails, which are both still in an early stage of development.

It is still anybody’s guess if scripting languages will catch on and maybe even replace the Java language, but with this Oracle announcement, languages like Groovy now have a better chance. Unless the marketing guys get to work very rarely does a technology become mainstream. We have a recent example of SOA, which many believe is an old idea recycled and hyped up.

The reason why Groovy and Grails are expected to do well is because although they introduce many new concepts meant to simplify development, they still stay close to the Java platform and enterprise Java development. While Groovy generates bytecodes that will run on the Java platform, Grails generates a J2EE application that can run on any J2EE server.

You can read more on Groovy on Grails in IndicThreads’ recent interview with the Groovy project lead Guillaume Laforge.

Related:
>> Programmers should let Java retire from the spotlight of web applications in dignity
>> Scripting Jython and Groovy using Coyote with NetBeans
>> Groovy bridges the scripting and the enterprise Java worlds
>> Jython vs Groovy
>> BEA to support scripting languages

The following two tabs change content below.
Content Team

Content Team

The IndicThreads Content Team posts news about the latest and greatest in software development as well as content from IndicThreads' conferences and events. Track us social media @IndicThreads. Stay tuned!
Content Team

Content Team

The IndicThreads Content Team posts news about the latest and greatest in software development as well as content from IndicThreads' conferences and events. Track us social media @IndicThreads. Stay tuned!

  • ‘Guest’

    An obvious counter-example is Ruby — a scripting language which certainly hasn’t yet died out. Why? Because Rails took off. So I think the answer to your question rests with how Grails will do. Though, Groovy also benefits from integration into several very popular Java frameworks. e.g. Spring has Groovy support now, to let you implement interface methods with Groovy (letting you change the implementation of a deployed application without having to reload). And if Grails can, at the architectural level, accomplish the elegance of Ruby, then it automatically ships with the plethora of Java third-party/open source libraries, as well as the wide deployment of JVMs. I’d certainly not count Groovy out based entirely on the fact that it’s a scripting language.

  • ‘Guest’

    Many scripting languages prior to Groovy showed promise but then died out. Maybe because the leads took up other things.

    Is there some reason why the same won’t happen to groovy?

  • ‘Guest’

    if it was 2.1, most concepts are not relevant to ejb 3.0