I have made a lot of progress this weekend on getting Groovy actions working with Spring's scripting support. The Spring guys have resolved a great number of issues with the scripting support in Spring 2.0.3.
My goals have been to allow a development style that uses Groovy, and the scripting support in Spring to eliminate a lot of the recompile, redeploy cycle. Using the Groovy Works technique I only need to restart my application for a change in configuration, or in a compiled java class. When I'm concentrating on one screen and its service bean, and DAO I can just code and basically hit reload in my browser. Spring and the Groovy Works plugin recompile the scritps as needed. Take a look: http://www.vitarara.org/cms/groovyworks Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]