The Blazing Grail – Part 3
Now that we have a working server it’s time to lock it down! The first thing we need is the ACEGI security plugin (Spring Security). These quick-start tutorials were very helpful to get started.
Read more
The Blazing Grail – Part 2
Hopefully you read the “into” to this short series. If not go ahead. I’ll wait . . .
Ok, so to begin at the beginning, let’s create a new Grails project. (I’m assuming you’re at least a little familiar with Grails. If not then read the Quick Start article; that should be enough to get you started.)
If you’re an Eclipse user (like me) then you can import this project right into Eclipse. The groovy plugin would probably be helpful and I’ve been pointed to the SpringSource Tool Suite (with the Grails extension) as a good tool to use (it’s what I’m currently using). Notepad2 is working pretty well for me right now too though.
From here you could either use Sébastien’s plugin which will install a nightly snapshot of BlazeDS4 and Spring-Blaze.
The Blazing Grail – Part 1
I’m not a server guy. I know just enough Java to get into trouble. I’ve paid bills writing PHP but I’ve never really felt “comfortable” with how things turned out; they worked and the client was happy so I got paid. But I often have to have things happen “back there”. I think rich clients are great; it makes sense to me (as a Rich Client Developer) to keep the logic where it happens. But sometimes that means that that happens up there on the server and I don’t always have a JavaMan handy to take care of it for me.
A short time ago a friend of mine (Ron Haberle) introduced me to Grails. And for me it sure is the holy grail. ”Convention over Configuration” makes sense to me (when, that is, I don’t have to BEAT the convention configuration into submission like using Maven with Flex projects). But for writing the simple server side logic that I’ve got to write, Grails is awesome.
