On 2/14/07 10:03 AM, "Dave Newton" <[EMAIL PROTECTED]> wrote:
> You can configure Spring2 beans to do this via the
> <lang:groovy.../> element.
>
> It's not clear to me if you can configure it so the
> Groovy action can be hot-compiled w/ a standard
> <bean.../> element but w/ a combination of refs or
> something I'd bet you could.
I did some research and found the Groovy actions in WebWork post from
Christian at Adigio. That doesn't work for me, because he was using WebWork
to instantiate his actions. I'm using Spring. So, that got me thinking about
making a bean factory that would do dynamic reloading of Groovy beans, then
discovered the Spring already does it.
I have Spring configured, but when it goes to instantiate the Groovy action
class from the script it's not on the classpath. My environment:
* Maven 2 (based off the Struts 2 Archetype)
* Jetty plugin
* Groovy source files mixed into src/main/java
I know my issue is that the .groovy files are not being copied from
src/main/java to the target directory. Problem is I'm pretty much a Maven
novice. In ant I'd just make a task to do it, but I have no idea how to do
that in Maven.
I'd like to get Jetty to just add the Groovy files to the classpath, and
additionally not restart the application server when a groovy class is
saved. Just leave the reloading to Spring.
Then I did some more research and it appears that Spring script beans are
strictly singletons. So, that won't work for Struts 2 actions.
(http://forum.springframework.org/showthread.php?p=101486) I'm going to
follow that thread on the Spring forum, and I'll report back when I've got
more information.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
