I think the stuff he's talking about is really part of Groovy, not
grails (could be totally wrong, of course). Groovy is pretty freaking
dynamic. :-)
Re: http://www.infoq.com/articles/aop-with-groovy
And as for the XML config of Spring beans, this is pretty tits:
http://www.grails.org/Spring+Bean+Builder
As for Grails / CF... well, I actually dicked around with the idea of
loading up grails (I think it's basically a spring application
context) in CF, but...
What's the point?
Grails has a swell rendering engine (.gsp's), makes tests for you,
etc., etc., etc..
FWIW, serving grails from CF looks totally possible-- the reason I was
wanting to do it was for GORM (I dig the way constraints and whatnot
are set up, but there are pluses and minuses to the approach), but
then I was thinking..
"Ya know, you could add the GORM-ish stuff to Reactor pretty easily
(or really whatever you'd like, as CF is pretty freaking dynamic
itself), and that way it would all be in CF, editable by CFers, etc.."
Eh. Another FWIW: custom tags seem to offer some of the aspects of
closures, tho not as flexible as what I think I see in Groovy...
Double eh. The way CF handles functions and whatnot means that
theoretically, you can do some pretty AOP-ish stuff right in CF...
but, again, I think the main deal here is... well, a good pattern so
things aren't super hard for the next dev to figure out + scale well
(or a similar thought-path-- just because you can do it, is it the
best approach? etc.).
I mention this stuff because it seems like you don't see many people
doing things like dynamically renaming origFunction to _origFunction,
and replacing it with the modified version (that maybe calls
_origFunction), tho it's totally doable.
Tripple eh. I'm snarfing down some noodles while doing some other
stuff, so sorry for the sadly disjointed post, but maybe there's some
info in here.
Peace and potatoes peoples! =]
:DeN*
--
Guys just don't care. We don't take the time to plan behind each
other's back. We just say, If you don't like me, screw you'. If a guy
doesn't like you, you know because you have a black eye.
Jonathan Bennett
That's more about how Grails handles controllers (and the support
Groovy has for closures of course) so you may find it more appropriate
to look at MVC frameworks for ColdFusion rather than expecting
ColdSpring to handle this. You might start by looking at ColdBox which
has the concept of interceptors...
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood