Comments on: Building a Grails App in ~40 hrs (part 3)

By: ALTERthought Blogs » Grails App in ~40 hrs (part 5)

ALTERthought Blogs » Grails App in ~40 hrs (part 5) — Thu, 03 Sep 2009 17:17:15 +0000

[...] Part 3: The first ‘technical’ post. JSecurity setup, initial Domain object created. [...]

By: Rafał

Rafał — Wed, 19 Aug 2009 11:47:09 +0000

Hi, nice job!
Is there any chance to download your code?

By: don

don — Tue, 18 Aug 2009 21:35:00 +0000

@kp… The JsecUserRoleRel is a construct created by the Quick Start process that holds which Role(s) a User belongs to. While there are technically no constraints on making in 1-M, M-M, etc, for our app we only need user to belong to exactly one Role… (in fact we don’t really even need a Role right now.)

Because we have no need for a Role, I could have simply had the Profile object directly reference the JsecUser object but I thought I would allow for a little leeway for any future expansion by holding a reference to the JsecUserRoleRel, which gets us access to both the JsecUser and the JsecRole object (should we ever need the Role for later stuff)

Hope this makes sense.

By: kp

kp — Tue, 18 Aug 2009 20:32:25 +0000

I don’t understand your use of JsecUserRoleRel in the Profile object. Isn’t JsecUserRoleRel a “many-to-many” between user and role?

By: ALTERthought Blogs » Grails App in ~40 hrs (part 4)

ALTERthought Blogs » Grails App in ~40 hrs (part 4) — Mon, 17 Aug 2009 15:04:03 +0000

[...] last post covered the kickoff to the ‘twodo‘ application– where we created our Grails [...]

By: don

don — Tue, 11 Aug 2009 15:43:54 +0000

@Oliver…that was just a bit of artistic drama :) I have actually successfully deployed it to both GAE and EC2 and will provide the details as to what level of effort was required in subsequent posts. But, you are fundamentally correct– EC2 was a _lot_ less painful than GAE.. that being said GAE is free and EC2 is not….

By: Olivier Gourment

Olivier Gourment — Tue, 11 Aug 2009 15:37:08 +0000

Nice post!
Just a comment about “we hope to deploy it to a cloud computing platform like Google’s AppEngine “. AppEngine has unfortunately so many limitations that most plugins don’t work, you have to use gorm-jpa (or jdo) and constraints won’t work… EC2 looks like a safer bet, considering the route you have taken so far.
Cheers