On 2/24/07 10:23 AM, "Mark Menard" <[EMAIL PROTECTED]> wrote:
> At this point I have scripted actions and service beans in Groovy, with > automatic reloading working. (http://www.vitarara.org/cms/node/98) A brief update. I have this working in a simple environment. I tried adding Spring declarative transactions using its aop pointcut support. This causes an exception when attempting to load the Groovy action because AspectJ can't get the type from its class loader and therefore can not determine what aspects to apply. This additionally makes me wonder if Spring's scripting support supports using pointcuts to configure transactions. I'm doing more research. Hopefully this will work. As an experiment I again tried creating a plugin that would create a GroovyClassLoader. In this plugin I make the servlet context classloader the parent of the GroovyClassLoader, then make the GroovyClassLoader the parent of the Spring class loader. With this class loader config I can load an action from a script and have Spring wire it, with pointcut support. (The AspectJ class loader is down stream from the Groovy one so it works.) This is quite messy, and only save a restart if you change an action. (If I could get Jetty to ignore the new .groovy file being copied into its classpath. Right now Jetty sees a new file on its classpath and restarts the container. I can turn this off, but it leads to a manual restart anytime I recompile a Java class. It's just not optimal.) Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
