2003. janu�r 15. 11:30 d�tummal Phase Web and Multimedia ezt �rtad: > But that is my whole point. Complex validation or not. Why don't we handle > both types of validation in the SAME class. I don't want to beat this into > the ground. But, it just seems organizationaly better in my mind to handle > validation on the Action level. With all the great minds on this project I > am certain that there is a good design reason for placing validate in the > ActionForm. I am just curious what it is.
I use the validator framework to ensure that the Form property (type String) can be converted to BigDecimal/Date/int. If I reuse a Form I want to reuse these validations as well. This can be done if the validation is coupled with the form imho. No one is forced to use this approach however. You can implement the other one by creating a new BaseForm base class which has the a function with the same functionality as the ValidatorActionForm.validate(...) under a different name. Set up the validator framework properly. This ensures client side validations, but the server side validation won't occure. Now call the renamed form's validation function in your BaseAction's validate method. Tib -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
