Re: [S2] Refactoring Action classes

[Al Sutton]

You don't need to have all your actions for a namespace in a single 
class, you can use multiple classes.

I usually group methods acting on a common object into a single class 
which usually leaves me with the 5 public methods in a class which map 
to actions (typically CRUD plus a View method), and multiple classes for 
different object types.

Imho 20 is too many, 10 is a lot, 5 is OK (don't forget that's public 
action methods, the number of private methods you have will depend on 
your app).

Al.


Milan Milanovic wrote:
Dear Al and Dave,

I tried to fix that error with session variable all weekend and I didn't
managed to fix it. When action is defined as redirect action to another
namespace, and when that action is called, another action called method
doesn't see my session variables. I just changed this redirect action to
that another namespace, as standard action (not redirect) and I now see my
variables! I don't have any idea why it doesn't work with redirect action,
but I'm SURE that there is some problem.

I have one question regarding refactoring action classes, is it much to have
20 actions per one namespace/action class ?

--
Regards, Milan
  


--
--
Al Sutton

W: www.alsutton.com
T: twitter.com/alsutton


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