Most often, the Actions work as an adapter between a view layer and a
general-purpose business facade. Because the Actions select a token
indicating a result, the Actions tend to be bound to some type of
navigational system. A classic Action passes input values to the
business facade, and the
I also personally think that defining actions in a
service tier doesn't smell right.
I'm not sure what you mean by that... it's just a
class; it happens to be compiled on-the-fly during
bean instantiation. Not much else is different.
Yes, but it feels to me like you are reaching back
--- Ian Roughley [EMAIL PROTECTED] wrote:
I'm not sure what you mean by that... it's just a
class; it happens to be compiled on-the-fly during
bean instantiation. Not much else is different.
Yes, but it feels to me like you are reaching back
into the business service tier to create classes
I remember seeing Groovy support on a blog for WebWork a while back. I
think the implementation was a new ActionProxy, so the groovy actions
could be scripted dynamically at run time and the page only needed to be
refreshed. For some reason, pre-compiling the groovy actions into class
files,
On 2/14/07 9:46 AM, Ian Roughley [EMAIL PROTECTED] wrote:
I remember seeing Groovy support on a blog for WebWork a while back. I
think the implementation was a new ActionProxy, so the groovy actions
could be scripted dynamically at run time and the page only needed to be
refreshed. For some
--- Mark Menard [EMAIL PROTECTED] wrote:
Oooh... I was thinking about something like that,
where you would not need
to keep reloading the application, but be able to
change the script, have it
dynamically recompile and simply hit reload. Kind of
like you can do with
JSP files under the
I think it was Chris from Adigio that had the blog entry. The proxy
basically always checked the filesystem for the latest .groovy script,
and then used it.
I'm not sure about Spring's groovy support, and whether it allows for
hot swapping. I also personally think that defining actions in a
--- Ian Roughley [EMAIL PROTECTED] wrote:
I'm not sure about Spring's groovy support, and
whether it allows for hot swapping.
You can define how frequently it will check the script
for updates, even.
I also personally think that defining actions in a
service tier doesn't smell right.
I'm
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
On 2/14/07, Mark Menard [EMAIL PROTECTED] wrote:
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
I've recently started using Groovy in my Struts 2 project to write my
actions. After some experience with it, I've written up a blog entry with
some quick examples.
http://www.vitarara.org/cms/node/95
Mark
-
To unsubscribe,
Very cool. Please add a link in our Struts 2 wiki [1] to it for
future reference.
Don
[1] http://cwiki.apache.org/confluence/display/S2WIKI
On 2/13/07, Mark Menard [EMAIL PROTECTED] wrote:
I've recently started using Groovy in my Struts 2 project to write my
actions. After some experience
On 2/13/07 12:54 PM, Don Brown [EMAIL PROTECTED] wrote:
Very cool. Please add a link in our Struts 2 wiki [1] to it for
future reference.
Done. I also added some of the other writeups I've done.
Mark
-
To unsubscribe,
Very cool. If only Groovy supported annotations so that the
configuration didn't need to be in the struts.xml file (but it looks
like annotation support is starting).
/Ian
Mark Menard wrote:
I've recently started using Groovy in my Struts 2 project to write my
actions. After some
On 2/13/07 3:22 PM, Ian Roughley [EMAIL PROTECTED] wrote:
Very cool. If only Groovy supported annotations so that the
configuration didn't need to be in the struts.xml file (but it looks
like annotation support is starting).
Ian,
From your lips to G_d's ears. I can't wait for annotations.
Yes, cool stuff.
You might also be interested in:
http://www.vim.org/scripts/script.php?script_id=490 ;-)
Tamas
On 2/14/07, Mark Menard [EMAIL PROTECTED] wrote:
I've recently started using Groovy in my Struts 2 project to write my
actions. After some experience with it, I've written up a
I read trough your blog entry. This is brilliant.
I'm a groovy newbie myself and I plan to tinker with Groovy actions.
Perhaps s2 might end up becoming a nice web platform for Groovy
in addition to Grails.
On 2/13/07 3:22 PM, Ian Roughley [EMAIL PROTECTED] wrote:
Very cool. If only Groovy
17 matches
Mail list logo
