Re: [Webwork-devel] Validation on commands?

[Matt B. <ma...@sm...>]

IMHO, I believe this is why it should be explicit. You have cases where it
should be shared, not used, and separate.

----- Original Message -----
From: "Rickard" <ri...@mi...>
To: "Low Heng Sin" <lo...@co...>
Cc: <web...@li...>
Sent: Tuesday, March 12, 2002 3:16 AM
Subject: Re: [Webwork-devel] Validation on commands?


Low Heng Sin wrote:

> non-cmd action - validate() -> doValidate()
> cmd-action - doDefault() -> doDefaultValidate()
> doEdit() -> doEditValidate()
> doCreate() -> doCreateValidate()
>
> The validate for cmd-action should be optional and implemented using
> reflection ( just like how cmd work ).


Preferably not. It is quite common (at least for me) that validation
rules needs to be shared between two or more commands, so splitting them
up is not a good idea.

/Rickard

--
Rickard Öberg
Author of "Mastering RMI"
Chief Architect, TheServerSide.com
   The Middleware Company - We Build Experts!


_______________________________________________
Webwork-devel mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/webwork-devel