Hi Dave,
Thanks for your reply. It makes perfect sense.
I should revisit my action classes and do some refactoring
Thanks,
ST
newton.dave wrote:
>
>
> Personally I tend to use multiple actions, mostly to avoid having
> unnecessary action properties. For me it's easier to deal with ma
Hi,
This is a general design practice question.
Say if I am designing User Account Management component that does the
following:
1) User Profile info update -- updates firs name, last name, etc,...
2) Change password. -- do password verification, and change password
3) User Payment info update. -
2 matches
Mail list logo