SpringOne 2GX 2009, New Orleans, LA

The conference was excellent.

The VMWare acquisition seems like it will be good for SpringSource. They want it to broaden their product offerings, and don’t have anything that directly competes. Beginning entry into Cloud computing with Cloud Foundry. You can either use it hosted by them, or install it in your own server room. All attendees will receive 48 hours of credit for use of Cloud Foundry, so I will definitely be experimenting.

Rolling out more developer editions of tools to entice us developers to use their tools. SpringSource Tool Suiteis now free, and incorporates additions for their entire line. It even has a deployment tool for Cloud Foundry.

They are actively developing the Groovy/Grails Eclipse pluginas well, and are making great headway here. At the conference, the developer had a very interesting presentation on the difficulties of integrating the Groovy compiler with the Eclipse JDT compiler.

tc Servernow has a developer’s edition too. In combination with the SpringSource Tool Suite, and Spring Insight, allows for digging into the actions an app took, and how long each step took. Have to do some investigation to see how well this works with a minimally Spring based app, as they used a Grails app for the demo.

Spent most of my time on the 2GX side of the conference. Decided to take the opportunity to learn more about this. Very interested in Groovy, especially since it interacts very nicely with Java. Several presentations on using Groovy to write tests for Java code, and some of the benefits possible as a result. Groovy (like other languages that are dynamic, and support closures and meta-programming) are very powerful and flexible. Groovy also requires less typing to achieve the same result as Java.

Attended 2 sessions on Gradle. The developers of Gradle developed it because of frustrations with the limitations of Maven. The developer presenting was obviously very familiar with Maven, as evidenced by his responses to questions by attendees that knew Maven very well. It leverages Maven and its central repository, and adopts Maven’s philosophy of convention over configuration BUT if you don’t like it’s convention, or want to extend it’s definitions, it is easily accomplished. Yay to a distinct integration test task, with its own classpath and dependencies!

Overall, an excellent conference, and I will post additional details as time permits.

It's only fair to share...
Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Leave a Reply