Grails-Melody plugin block closure about javamelody HOT 3 CLOSED

Hi,

I don't know if it applies to your case, but have you seen the following thread 
in the grails user list:
http://markmail.org/message/d7insscax6xtlht5 ?

And as Burt said:
"Why would you want a closure in a Service? Closures are executable like methods
but are ignored by Spring, so they cannot be transactional or be proxied in any
way."

That said, what exactly would you change in the grails plugin in order first 
not to break anything and then to fix this issue:
http://plugins.grails.org/grails-grails-melody/trunk/GrailsMelodyGrailsPlugin.gr
oovy ?

Thanks

it was me created that ticket. 

I already change lot of my codes to use method instead of closure, but this 
case is different, it is kind of a visitor pattern and I don't want to create a 
big list of sub classes to do the things can be handled by a single closure, 
and there are no transactions involved. 

Thanks to a patch from Jean Barmash, committed in svn by Liu Chao (rev 67953), 
this issue with closures is supposed to be fixed. It is ready for the next 
release of the grails plugin (1.0).

http://plugins.grails.org/grails-grails-melody/trunk/GrailsMelodyGrailsPlugin.gr
oovy