Chariot Training Classes

Training Courses

I run Chariot's training and mentoring services. We provide training in AngularJS, HTML5, Spring, Hibernate, Maven, Scala, and more.

Chariot Education Services


Chariot Emerging Tech

Learn about upcoming technologies and trends from my colleagues at Chariot Solutions.


Chariot Conferences


Entries in grails (17)


Chariot TechCast Episode # 22 - Chris Richardson

I've just uploaded the latest Chariot TechCast, Episode #22. In this episode, I speak to Chris Richardson about Cloud Foundry, Cloud Tools, Grails and Amazon Web Services. He's speaking at the Philadelphia Emerging Technologies for the Enterprise conference on March 26-27.


Grails 1.1 Beta 2 Released

Just announced Grails 1.1 Beta 2. This release includes maven integration, including building your grails app from maven, or using an archetype to create Grails projects.


Grails acquired by SpringSource... A Good Thing

I've been thinking about the recent acquisition of G2One by SpringSource, and I've come to the conclusion that it was a very bold and smart move by both parties. Why? Simply because it provides benefits to both parties and gives those who need rapid web development another alternative to Rails, only that runs natively in the JVM and can access all of their existing Java EE infrastructure.

I should note that my employer, Chariot Solutions, is a consulting partner with SpringSource as well as with several other firms such as RedHat/JBoss.

SpringSource gains a lot by adding this web framework. First of all, it now has an agile web platform, based on Spring and other open source technologies, that it can support for larger corporate customers. This may bring agile web development into more enterprises, as most have shied away from Groovy/Grails simply because it was too new, ran on a maverick language (Groovy) and had a small support team.

Second, SpringSource extends its team of experts to include the talented Grame Rocher, a great addition to their team who brings an offbeat and innovative perspective to application development. I understand they may use some of his time to help them with Spring Core, and as he says in his interview on Grails Podcast Episode 72, this acquisition will actually give him more time to work on Grails than he had when G2One was independent.

From G2One's side, they gain a huge support staff, with the ability to fix bugs in the platform, add staff to commit to Grails 1.1 and beyond, and for new projects, such as revamping Grails' Eclipse plugin support. Not to mention the fact that Groovy/Grails makes the enterprise more productive, I think we will start to see a lot of new prototyping efforts as people start kicking the tires and discovering the big productivity gains that will await them once they give it a try.

If you haven't given Grails a try, and you're a Java developer, you should. It's a compelling platform for application development, and has a growing community.

Some upcoming features of Grails 1.1 mentioned in that podcast above:

  • Maven Support (Really, Graeme? Wow, I know that must hurt a bit! ;)

  • Customized templates are now honored when installed with grails install-templates

  • JSP taglib support in GSPs

  • Plugins now are stored outside of a Grails project, and the project metadata references the plugin. This means no more checking in plugin code to source code repositories. What's more, when a project is checked out, the plugins are automatically installed, ala transitive dependency management.

  • GORM now allows basic type collections like Strings

  • Data binding now can use a subset of the data from an HTTP request using the subscript operator

  • Read-only access to domain objects using

  • Default sorting order in Domain classes, associations

  • The new Testing Plugin is now the standard way to test in Grails.

And a whole lot more. Read up on the Grails 1.1 feature list in the Beta release notes page on


Nice job on the interview, GrailsPodcast guys!

Technorati Tags: , , ,


SpringSource acquires G2One

From PC World and other sources...

SpringSource just purchased G2One, the company backing Groovy and Grails. I think this is a great, if somewhat expected, move, for several reasons:

First, G2One is giving SpringSource the agile development platform it needs to stay competitive with other Java-based rapid application platforms, such as JBoss Seam.

The Seam framework seems to be geared toward building applications rapidly, gluing together JSF front-end web applications with back-end EJB, JPA and Hibernate. From my limited research, it seems to do a pretty good job at simplifying JSF and at gluing together components into a simple, easy to access context. However, Seam still generates lots of descriptors, and is more heavyweight when it comes to deployment (you generally should deploy in a full container such as JBoss). You could argue that Seam, while building more heavyweight components, still runs the standard Java EE component stack.

Grails is a tremendously productive platform. You can build applications using Groovy, taking advantage of the dynamic typing and closures, as well as the fantastic GORM relational mapping tool (which is backed by Hibernate). The front-end supports scaffolding, so that you can dynamically generate prototype web pages for CRUD operations, all while validating and imporoving your domain model.

Reading through the Merger FAQ, it appears that G2One users will be able to gain support by purchasing a SpringSource license, SpringSource / Covalent will now help maintain / enhance Grails, and that they will keep the framework free via the Apache Software License.

This will be a huge leg up for the Grails platform and the Groovy community. I'm looking forward to seeing more Grails opportunities in the future.


Setting up the IntelliJ Plugin for Groovy and Grails

The IntelliJ plugin is a great tool. However, one important thing to note is that it wants the source distribution of grails in the grails directory. Why? Because the GSP support requires the source code for the GSP tags.

Plugin Setup Process

In order to properly set up the Grails plugin, do the following:

  1. Download the grails source code zip file (which also contains the binary)

  2. Unzip the source code distribution

  3. Download the Groovy source and binary code distributions. Since the source release does not include a built binary, I had to download both the source and binary distributions and merge them together (building on my OS X machine failed). YMMV.

  4. Open IntelliJ Idea, go to the Preferences / Plugins page, and download JetGroovy and install it

  5. Restart Idea

  6. Open the Preferences / Plugins page again, and select Groovy

  7. Set the folder locations for Groovy and Grails to your new directories

There, that's it. Now, you can create Groovy and Grails projects, debug Groovy code, and use the Apple/Ctrl click trick to jump into Groovy or Grails source code.

GSP Tags

GSP tags are closures, so the plugin can't figure out attributes. That's ok, if you want to see more information, just CTRL or Apple click on the GSP tag name, and it will jump to the source code of the tag closure in the editor.