InfoQ

News

Groovy gets a contribution from Oracle; ongoing Grails contributions discussed

Posted by Floyd Marinescu on May 17, 2006 02:39 AM

Community
Java
Topics
Web Frameworks,
Scripting
Tags
Grails,
Groovy,
Oracle,
Ruby on Rails
Oracle has recently contributed an extension to the Groovy JMX MBean that will aid in managing Java apps with Groovy.  Oracle sees the ability to use scripting languages and Groovy in particular to administer, monitor, and deploy apps as something the community needs.

An ongoing contribution is currently being discussed between Oracle and the Groovy and Grails leads about Oracle's intention to contribute ongoing engineering and QA resources to the projects.   Oracle will initlally contribute QA teams to make Grails work on Oracle's appserver, and discussions are beginning about donating resources to make the Java Persistence API (JPA) work under Grails (as an alternative to Hibernate).

Groovy is getting a lot of exposure at Java One  and Oracle's Groovy guy Tugdual Grall spoke to InfoQ about Oracle's contribution. "We want to facilitate the development experience so  frameworks like Grails and Ruby on Rails are great at doing this, but while we're interesetd in JRuby, what you need for the enterprise is an IT integration strategy. How is your web app integrated into your organization's IT management and deployment strategy?"   Oracle sees Grails as potentially having better chances for mainstream adoption because "at the end what you generate with Grails is a J2EE app, web container managed and deployed. You can manage it in the same way you manage any other J2EE app."

3 comments

Reply

IDE, IDE, IDE by Horia Muntean Posted May 18, 2006 6:34 AM
Re: IDE, IDE, IDE by Tug Grall Posted May 18, 2006 5:40 PM
Re: IDE, IDE, IDE by Horia Muntean Posted May 19, 2006 2:55 AM
  1. Back to top

    IDE, IDE, IDE

    May 18, 2006 6:34 AM by Horia Muntean

    Better IDE support for groovy would be nice !

  2. Back to top

    Re: IDE, IDE, IDE

    May 18, 2006 5:40 PM by Tug Grall

    Hello Horia, I am totally with you on that; but Groovy has already a nice integration with Eclipse to write, run and debug scripts ( http://groovy.codehaus.org/Eclipse Plugin ). One of the hard part about the IDE and Groovy is related to one of the benefits of Groovy: it is a dynamic language. So it makes sometimes hard to support some basic features such as code completion are very challenging... How the IDE would know how/what to complete since you are invoking a dynamic method/property that does not exist in the object.. However, I am very very interested to know the kind of features you would like to see for a Groovy editor... Regards Tug http://blog.grallandco.com

  3. Back to top

    Re: IDE, IDE, IDE

    May 19, 2006 2:55 AM by Horia Muntean

    Hello Tug, I am aware of the dificulties dynamic languages bring to code completion, refactoring ( some say they are even imposible ) but syntax coloring is not enough. Partial code completion would be nice, code templates, automatic imports, etc. Regards, Horia

Exclusive Content

Rustan Leino and Mike Barnett on Spec#

Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.

10 Ways to Screw Up with Scrum and XP

Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.

Tips from a Top Sports Team Coach

This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.

SOA Governance: An Enterprise View

Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.

Developing Portlets using JSF, Ajax, and Seam (Part 2 of 3)

This article covers setting up a RichFaces portlet using JBoss Portlet Container and JBoss Portlet Bridge, deploying a RichFaces portlet, and RichFaces capabilities.

Scalability Worst Practices

This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.

Do the Hustle

Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and give tips how Ruby developers can work with clients.

Natural Laws of Software Development - Deriving Agile Practices

Jeffries and Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense.