What i do, cuz i'm a little intellectually lazy, like Ray, is to place
a validate
function in my bean. Others abstract the validation to a separate
object, but i
prefer having it in one package. It's just a little easier for me to
see what's
going on.
I think there are two different kinds of
Nice to see a posting that isn't spam!!!
RADEMAKERS Tanguy said:
- On the one hand, you have a type of format checking that's essentially
about type safety, and that operates on single fields. If you have an object
that exposes an email address field, you expect that field (if it's
populated) to
Only if all of your validation is against single objects or manageably
small collections of objects. What happens if you want to import a large
number of users - perhaps using an uploaded csv file?
Peter I'd have to agree with your recommendation to remove the validation
from the object.
Hi Jason,
Firstly, I agree 100% with it depends. There is no right answer for all
cases. Many applications will never need editing of large collections of
objects, so the bean approach will be the best approach.
Secondly, duh - good point. 1 object and load 2000 times does make a bunch
more
