Grails 2.x uses it's own configuration loader that includes the ability to read extra configuration from additional, external files. This is a great feature for reading production, deployment specific configuration values; while keeping them separate from a standard WAR file. I've found this very handy when the same application needs to be deployed to multiple machines with only some configuration …
Soon after I updated my super simple grails download and launch script (on github) with the new download locations and other small tweaks for Grails 3 support. Grab the updated script from github then try out Grails 3 with:
Some while ago now, I considered the question of Grails vs Django as my web development framework of choice. Since then I've createda few Django web applications. I've also continued to work on several Grails based projects, newandold.
So with fresh battle experience of both frameworks I thought I'd revisit my previous thoughts to see what …
One of the projects that has been filling, a little too much at times, my recent non-parenting hours is now accepting entries.
The site is an addition to the Infiniti Formula 1 press site to provide competitions for people to design Formula 1 helmets (or a small non-advertiser section of them) that Sebastian Vettel will wear later in the season. …
Update: I revisited this Grails vs Django discussion in Jan 2015.
Before I met Grails I had spent several years writing my web applications in Perl, including work on two different in-house frameworks to try to make life easier! I also dabbled a little with Ruby on Rails but for some reason it just didn't stick (I think I prefer …
Quite a long time ago I talked about setting envelope sender addresses so that I could send mailshots and get back any bounces in a useful way. The missing component to it was to process those bounces within my application. Here, finally, is my write up of how I did this.
After much searching I eventually found the excellent SubEtha …
Please see Part 1 for the start of this series and links to all parts.
For the SupaJam ticket outlet, we didn't need anything too fancy, just enough to present people with a couple of ticket types to choose from and a way to pay for them. Of course we still had the extra requirement of collecting a real name …
Towards the end of May, SupaJam launched the first round of several festival ticket give aways planned for this summer. This wasn’t the first time SupaJam has given away festival tickets, but it is the first time that we've done it in this way.
Technically, it all went well. The days afterwards did include a rather large number of support …
However a change to that patch was suggested and before I managed to implement it, the mail plugin underwent a fairly large refactoring which meant I needed to …
I work with grails quite a lot these days. I have about 5 plugins and over 10 projects that I currently work on frequently. Fairly inevitably they use an assortment of grails versions. Manually chopping and changing command lines to execute different versions gets pretty tedious.
The Groovy HTTPBuilder library is extremely useful for interacting with all sorts of things, including remote web services that send back XML responses. In these cases HTTPBuilder will automatically use Groovy's XmlSlurper to parse the response and give you back a GPathResult to make navigating the XML super easy.
However today I've been trying to parse XML that's returned (from …
I would have expected the desire to set a specific envelope sender address for mails from a web-app to be fairly common. However finding information on how to do it with the Grails mail plugin (ie Spring mail (wrappers for JavaMail)) proved much harder than I expected.
I ended up reading the Grails code to figure this out, so I thought it might be useful to record.
One of the projects that I recently upgraded to Grails 1.2 makes use of Groovy HTTP-Builder. If you just pull in HTTP-Builder you'll quickly find that it's dependencies break your grails project. So under 1.1.1 and using maven, I …
Following the recent release of Grails 1.2.0 I've attempted to upgrade a few of the projects I work on. Some of these attempts have gone better than others.
For one of the simpler ones I only hit two problems.
Combining Acegi with Enum's defined in the same source file as domain objects no longer works. The grails bug is here …
The Grails mail plugin is an invaluable addition to most Grails based sites - it's a rare website that doesn't need to send email. Some really useful features have been sitting on it's todo list for a while, but it still does a lot as it is.
Grails 1.1.1 has been out for a while now. For those people who use grails directly the upgrade path is pretty simple (download, install, run "grails upgrade"). However for those of us who haven decided to build our projects via maven, the path seems to be much less clear.