Summary

Well, this was a productive iteration. We implemented our task-related features, and along the way, we learned about Grails service classes, integration testing, and what it takes to modify or extend a Grails domain class after we’ve generated the code. Take a break. You deserve it! Catch up on some blogs (http://groovyblogs.org would be a good choice) or email. Next we will work on adding a message forum and see what we can learn while we’re at it.

Footnotes

[50]

See http://docs.oracle.com/javase/6/docs/api/java/text/SimpleDateFormat.html.

[51]

See http://groovy.codehaus.org/Collections.

[52]

DRY stands for Don’t Repeat Yourself. This is one of the core principles in The Pragmatic Programmer [HT00].

[53]

You can find more details ...

Get Grails 2: A Quick-Start Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.