I think the behavior of whether to terminate field level checking on the first field failure should be controllable. For my company's application, it is important to show all the failures for a given field, so the user knows that not only is the field required, but it's a telephone number field which has a specific syntax (say). Right now, and even with the proposed changes, Struts validator doesn't let me do that -- it has a hardwired policy of stopping on the first field error. I am ok with that being the default behavior, but I do think it should be configurable.
Steve > -----Original Message----- > From: phpsurf [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 20, 2002 1:20 AM > To: Struts Developers List > Subject: RE: VOTE: Behavior of Validator > > > +1 definitely > > I definitely agree with both: > - The validation process should first iterate through all > fields and then, > for each field, iterate through its scpecific validation rules. > - The validation process can stop (for each field) at the > first unvalidated > rule, but it should not stop at the first unvalidated field ... > > > > -----Original Message----- > > From: James Turner [mailto:[EMAIL PROTECTED]] > > Sent: jeudi 19 septembre 2002 19:41 > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: VOTE: Behavior of Validator > > > > > > As currently written, the Validator has what I consider a quirk. > > > > Suppose you have two fields, username and password. Username has > > "depends=required" and password has "depends=required.notgod" > > (where notgod > > is a test that makes sure that the user didn't choose god as a > > password). The following behavior occurs: > > > > username=blank, password=blank: two errors generated on "required" > > username=blank, password=god: one error generated on "required" > > username=george, password=god: one error genereated on "notgod" > > > > This is because the Validator won't look at notgod until *all* > > fields pass > > the "required" test. > > > > I think this is a broken behavior. It leads to web forms > where the user > > thinks that they've filled in all the fields correctly, but > then get new > > error messages they've never seen before. I'd like to correct > > this before > > Validator freezes for a release, but I want to make sure no > one really > > really thinks that the current behavior is somehow the > right one. So > > please vote: > > > > +1 = Change Validator so that this doesn't occur > > 0 = I don't give a hoot > > -1 = I really like the way it works now (please give a reason) > > > > I'm sending this both to Commons and Struts because both > communities are > > impacted by the change. > > > > James > > > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > ________________________________________________________________ > Etudiant: Wanadoo t'offre le Pack eXtense Haut Débit soit > 150,92 euros d'économies ! > Et pour 1 euro de plus, reçois le CD-ROM du jeu Dark Age of Camelot > + 1 mois de jeu en réseau offert ! > Clique ici : http://www.ifrance.com/_reloc/mail.etudiant > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
