why conditionally? if they are both null the check will still pass.... -igor
On Wed, Feb 27, 2008 at 2:57 PM, Vitaly Tsaplin <[EMAIL PROTECTED]> wrote: > I am using it. But I was going to attach it conditionally... > > > > On Wed, Feb 27, 2008 at 11:44 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > have you seen EqualPasswordValidator? > > > > -igor > > > > > > > > > > On Wed, Feb 27, 2008 at 2:33 PM, Vitaly Tsaplin > > <[EMAIL PROTECTED]> wrote: > > > Hi users! > > > > > > Next question from newbie's series. :) > > > I have a password field but since I am doing an account update, I > > > am not going to enforce user to change his/her password. So in this > > > case I mark both a password & a confirmation fields as optional > > > (required = false). But in case if an entered password is not empty it > > > appears that the user has an intension to change it and it means that > > > I should perform a usual validation step (password & conformation > > > required and should be equal). So my question is... in which method I > > > can check the presence of a password and turn on a validation back > > > before the actual validation will happen? > > > > > > Best regards, > > > Vitaly > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
