Seems like Remi and I had a discussion about this a few weeks ago. I've
been kind of waiting for someone else to give it a go before I dove in.
I'd suspect Tim's crazy admin action bean is a rare case. The only
thing I see that would make using Groovy over straight Java a non-issue
is that a good ActionBean isn't that complicated and getters/setters can
be generated by the IDE. So can anyone make a *real* case for why
Groovy would be worthwhile in this case?
Don't get me wrong. I love gant and I like using Groovy for quick and
dirty prototypes and like Remi enjoy it more than shell scripts. But
outside of Grails considering everything else Grails does, I'm not
sure. Unless we moved the Stripes annotations into something more like
Grails constraints I just don't see the pay off.
Gregg
Freddy D. wrote:
> Thanks for the info. Like you, I tried Groovy pre-1.5 support and
> really liked what I saw. Especially being able to use closures in
> mappings and iterations, which I love (and why I wrote
> FunctionalJ to tide me over until something better would become
> available).
>
> I always thought Groovy+Stripes would be a very nice
> combination. So thanks for confirming that now with the 1.5
> support, it is indeed a workable solution.
>
> Cheers,
> Freddy
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
Stripes-users mailing list
Stripes-users@...
https://lists.sourceforge.net/lists/listinfo/stripes-users