Hey all,
After reading the [Poll] action mappings thread, I now have a couple of
design questions. I've got a lot of actions right now and I'd like to
group related functionality into one action. I'm thinking of extending the
DispatchAction and creating functions to
version that reads this parameter
instead of the request parameters.
But I'm wondering if there isn't a better way.
-Original Message-
From: Graham Lounder [mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 8:13 AM
To: [EMAIL PROTECTED]
Subject: Action Design Question
Hey all
Graham Lounder wrote:
Hey all,
After reading the [Poll] action mappings thread, I now have a couple of
design questions. I've got a lot of actions right now and I'd like to
group related functionality into one action. I'm thinking of extending the
DispatchAction and creating functions to
I don't know if this was the 'right' thing to do, but I extended
DispatchAction, overrode the execute method to use the hardcoded value
rather than looking up a request parameter, and pass that along to
dispatchMethod. My actions then inherit from this modified class. You
can safely cut out
[mailto:[EMAIL PROTECTED]
Sent: Friday, September 26, 2003 11:00 AM
To: Struts Users Mailing List
Subject: Re: Action Design Question
I don't know if this was the 'right' thing to do, but I extended
DispatchAction, overrode the execute method to use the
hardcoded value
rather than looking
5 matches
Mail list logo