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 serves one function. If you work in a team environment, it also tends to make it a little easier to coordinate efforts (note hugely so, but enough that I prefer it).

Some say that more classes makes the overall system more difficult to understand. There certainly is something to that, however, proper packaging can largely alleviate that problem (i.e., don't have one big Actions package with all your Actions, break it up into functional groups so you have a few Actions in each group).

In the end though, it really largely just comes down to preference, and what your own experience tells you. There isn't at this point any clearly defined "best practice" in this regard, not that I'm aware of anyway.

So, no, to answer your question directly, it is definitely NOT required to write separate actions for each mapping. Whether that's the best approach or not is a much more difficult question to answer :)

Frank

chamal desilva wrote:
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 organize actions in to action
classes.

Thanking You,
Chamal.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
Java Web Parts -
http://javawebparts.sourceforge.net
Supplying the wheel, so you don't have to reinvent it!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to