Comments on: Interrogating Arbitrary Groovy Closures for Values

By: Blog bookmarks 01/26/2010 « My Diigo bookmarks

Blog bookmarks 01/26/2010 « My Diigo bookmarks — Tue, 26 Jan 2010 06:26:03 +0000

[...] Interrogating Arbitrary Groovy Closures for Values – Ted Naleid [...]

By: Tweets that mention Interrogating Arbitrary Groovy Closures for Values - Ted Naleid -- Topsy.com

Mon, 25 Jan 2010 17:57:24 +0000

[...] This post was mentioned on Twitter by Debasish Ghosh, Dmitriy Kopylenko, HamletDRC, Ted Naleid, Zak Jacobson and others. Zak Jacobson said: @bradfordcross Look familiar? how to interrogate Groovy closure values without evaluating the closure: http://is.gd/6YVKl (via @TedNaleid) [...]

By: tednaleid

tednaleid — Mon, 25 Jan 2010 14:23:05 +0000

@Wolfgang – good suggestion about the try/finally (cloning would also work). I’ve modified the post to include it.

By: Wolfgang

Wolfgang — Mon, 25 Jan 2010 12:06:03 +0000

Thanks for the tip!

Just one thing: I would wrap calling closure() in a try {} finally {} statement, so that the delegate and resolve strategy are reset, even if an exception was thrown. Another way would be to clone() the closure, as described by Peter Ledbrook in his blog: http://www.cacoethes.co.uk/blog/groovyandgrails/supporting-reloading-in-your-grails-plugins