Michael Jouravlev wrote:
Chamal, if you decide to use a dispatch action, I suggest
EventDispatchAction, or ActionEventDispatcher if your action class
must inherit from your custom class. See these links:
Definitely agreed there... this is, to me at least, clearly the best
alternative if you go
Hi,
I have few action mapings.
/get_admin_tasks
/add_task
/ass_user
etc.
/get_add_data
/save_customer_data
/save_account_data
etc.
Is it necessary to write Action classes for each of
these actions or can we group several actions in to
one Action class.
What is the best way to
Depending on what version of Struts you are using, you could check out
org.apache.struts.actions.DispatchAction and it's subclasses. For the
sake of maintainability and readability though I generally prefer to
keep a 1 to 1 between action subclasses and path mappings, factoring
common
You ask a question that is frequently debated around here :) I can say
with quite a bit of confidence that Michael Jouravlev will be around
shortly to say DispatchActions are the ONLY way to go :)
I'm in the same camp as Adam though... I find that code is better
organized when each Action
On 6/7/06, Frank W. Zammetti [EMAIL PROTECTED] wrote:
You ask a question that is frequently debated around here :) I can say
with quite a bit of confidence that Michael Jouravlev will be around
shortly to say DispatchActions are the ONLY way to go :)
Not the only way, just the one preferred
I'll suggest wite a dispatch action and provide a actionmapping and call the
corresponding method in the Your action class.
On 6/8/06, chamal desilva [EMAIL PROTECTED] wrote:
Hi,
I have few action mapings.
/get_admin_tasks
/add_task
/ass_user
etc.
/get_add_data
6 matches
Mail list logo
