InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Groovy gets a contribution from Oracle; ongoing Grails contributions discussed

Posted by Floyd Marinescu on May 17, 2006

Sections
Development
Topics
Scripting ,
Web Frameworks ,
Java
Tags
Groovy ,
Grails ,
Ruby on Rails ,
Oracle
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."
IDE, IDE, IDE by Horia Muntean Posted
Re: IDE, IDE, IDE by Tug Grall Posted
Re: IDE, IDE, IDE by Horia Muntean Posted
  1. Back to top

    IDE, IDE, IDE

    by Horia Muntean

    Better IDE support for groovy would be nice !

  2. Back to top

    Re: IDE, IDE, IDE

    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 ( 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 blog.grallandco.com

  3. Back to top

    Re: IDE, IDE, IDE

    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

Educational Content

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.