One of the handiest features of Grails is the "flash" scope. The flash scope is "A temporary storage map that stores objects within the session for the next request and the next request only, automatically clearing out the objects held there after the next request completes." It's a handy way to send messages and errors around when dealing with form posts and redirects. Since I've been working with Spark Java I've found myself missing this little feature so I decided to throw together my own implementation. I've added the following closure inside of my
main() method in my
To manage the lifetime of the scope, I've added the following in my
after() filter. It limits the lifetime of any flash scoped variable to 2 requests:
To read from the scope:
To write to it:
flash(request, 'key', 'value')
For convenience the write method also returns the value meaning you can do things like this:
To return then entire flash scope:
I've written many blog posts about connecting to an Autonomous DB instance in the past. Best practices evolve as tools, services, and frameworks become...
Email delivery is a critical function of most web applications in the world today. I've managed an email server in the past - and trust me - it's not fun...
In my last post, we looked at the technical aspects of my Brain to the Cloud project including much of the code that was used to collect and analyze the...