I use DispatchAction for CRUD activities in my application. Using
methods like "create", "populate", "update" etc. I manage each
particular activity for my entity (e.g. User) but in some of these
activities I need validation (e.g. update/create) and in some of them
not (e.g. populate/delete). Currently I have double mappings like
/User.do and /UserVal.do for my (the same) UserAction DispatchAction.
One mapping is defined with validation and another without it. When I
want populate/delete method I use User.do mapping, and if I want
create/update methods I use UserVal.do mapping. Is there any better
approach for this?
Stjepan Brbot
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]