ALTERthought Blogs Archives: Groovy/Grails
next page ·
18 September 2009
Grails and Cloud Computing: Part 1 – Amazon EC2
Progress to Date
This entry is a part of the ‘What can you build in 40hrs‘ series– which, in a nutshell, involved an experiment to see what we could build in about typical weeks worth of work. In the last post we effectively completed the basic functional requirements of the application, and now have a [...]
continue reading... » 8 Comments
3 September 2009
Grails App in ~40 hrs (part 5)
Welcome back to our effort to build a Grails app in less than a week. This post will cover the final functional aspects of the application, after which we can move on to trying to deploy the app into a Cloud Computing platform.
To recap briefly our progress to date:
Part 1: We introduce the basic [...]
continue reading... » 8 Comments
17 August 2009
Grails App in ~40 hrs (part 4)
The last post covered the kickoff to the ‘twodo‘ application– where we created our Grails application, wired in JSecurity via plugin, and created a few of the core Domain objects the system will need.
In this post we will refine the general look and feel of the User Interface, as well as start building the core [...]
continue reading... » 5 Comments
10 August 2009
Building a Grails App in ~40 hrs (part 3)
In part 1 and part 2 of this series we introduced a challenge to build a reasonably non-trivial application in just a week. We have decided on Grails as the primary technology framework, and once we have a prototype working, we hope to deploy it to a cloud computing platform like Google’s AppEngine [...]
continue reading... » 7 Comments
3 August 2009
Building A Grails App in 40 hrs
In a prior post, I talked about an experiment — to build a working task management application in about 40 hours.
The high-level constraints governing the experiment were as follows:
The application should be web-based and ‘modern’ (AJAX, friendly URL’s, etc)
It should be reasonably non-trivial.
It should be developed as it were going to someday become a Software [...]
continue reading... » 9 Comments
7 July 2009
What can you build in ~40 hours?
My biz partner and I were relaxing over a few beers the other week and discussing recent trends in software development, agile methodology, etc (and our use of these trends over the past 7-10 years). At some point in time, we started talking about how little time 40 hours (i.e., a ‘typical’ work week) really [...]
continue reading... » 3 Comments
5 September 2008
Grails Testing Tip (DO’s, DONT’s and DOH’s): Fixture Data vs. Dependent Data
DO: Distinguish between Fixture Data and Dependent Data
Integration testing can be painful enough under the best of circumstances. Confusion around where data comes from, when it should be deleted, rolled back or committed can derail the even the best laid plans. (This is especially true in more complicated projects that involve multiple datasources, that [...]
continue reading... » 0 Comments
2 September 2008
Terracotta Plugin for Grails
I have created a new Grails Plugin to help in the development of Grails applications clustered using Terracotta. The details of this plugin can also be found at http://www.grails.org/Terracotta+Plugin.
Terracotta is a Java infrastructure that allows you to scale your application by clustering JVMs.
Features
Generation of a terracotta configuration file
Generation of terracotta enabled start up scripts for [...]
continue reading... » 6 Comments
26 August 2008
Grails Testing Tip (DO’s, DONT’s and DOH’s): The Clean Slate Principle
DO: Follow the Clean Slate Principle
Its happened to all of us, a test that was working just fine, suddenly starts failing because the test database was left in an unstable state. Enter the Clean Slate Principle.
Grails integration tests should endeavor to follow a simple rule:
Leave the database in the state in which you found it.
In [...]
continue reading... » 6 Comments
15 August 2008
Grails Tests: Cannot send redirect – response is already committed
When testing controllers, if you make more than one call to a action/closure you may get the error: “Cannot send redirect – response is already committed” But if you want to call one action to modify the database and then test the results in a subsequent call, if you put that call in a [...]
