I have spent the last week working on integrating Struts 2 and Groovy. I started writing my actions in Groovy last week. This is great, but I want to eliminate the compile restart cycle for general editing and debugging.
My first attempt was to extend the Struts 2 Spring plugin, to use a GroovyClassLoader to load my action scripts. This failed due to issues with AspectJ. (Spring uses AspectJ to do declarative transactions.) (Thread on Spring forum: http://forum.springframework.org/showthread.php?t=33896) So, I abandoned that and decided to patch Spring to allow for "prototype" script beans. (The default implementation of Spring scripting only has support for singleton beans.) This works fine. I have submitted the patch via the Spring JIRA, so we'll see what happens there. (http://opensource.atlassian.com/projects/spring/browse/SPR-3161) At this point I have scripted actions and service beans in Groovy, with automatic reloading working. (http://www.vitarara.org/cms/node/98) Now, I'd like to work on the development environment a bit. Right now I have to run 'mvn compile' to copy my .groovy files from my src/main directory to the target/classes directory for Jetty to see them. I'd prefer that Jetty add src/main/groovy to its classpath. This way I could just edit my groovy file, save, then reload in my browser. Quick, clean, and easy. I have looked at the Jetty docs (http://www.mortbay.org/maven-plugin/howto.html), but nothing here seems obvious. I've tried setting the classesDirectory, but I need it to watch both target/classes and src/main/groovy, and this option seems to only take one directory. I've also tried scanTargets, but that doesn't actually seem to be added to the classpath. If anyone has ideas I'd be happy to hear them. Thanks, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
