Not always.
An Action should be created to perform a specific control instance. For Example, if you are going to insert a record, the Action class has all the required code to insert the record. However, as you get into more complex systems, you will often find that you are duplicating a lot of the same functions. At this point you have to abstract many of these functions into utility or helper classes to reduce the amount of duplication that you have. This reduces your action class down to simply flow control logic. But if this becomes highly repetitive, then you may breakout into calling multiple actions that know how to handle a specific set of events.
"Lance Semmens" <[EMAIL PROTECTED]>
07/26/2005 12:24 PM
|
|
I'm a newbie to struts and I'm maintaining what I consider to be
spaghetti code.
There actions which forward to other actions and I'm getting lost a bit
lost at times.
As a rule, should an action be all encompassing and therefore not need
to forward to another action?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
