We used to have an EqualPasswordInputValidator as passwords in the store should always be one-way encrpyted and the comparison wasn't exactly the same as EqualInputValidator. Wickets internal structure however has changed obviously and the issue is handled differently.
Juergen On 5/9/06, Bruno Borges <[EMAIL PROTECTED]> wrote:
Besides the bug of having those two components not Serializable (which throws an Exception while trying to bind them to HttpSession automatically by Wicket), how about make EqualPasswordInputValidator a subclass of EqualInputValidator? There's only one difference: the key of the message to be displayed. Anyway... why there's a EqualPasswordInputValidator?! This way, there should be EqualLoginInputValidator, EqualBirthdayInputValidator, etc... :) if the developer wants to put more than one EqualInputValidator in the same form, he/she could specify the Key of the message in the constructor. FormInput.properties --> inputForm.SomeUserKey.EqualInputValidator=bla bla bla... FormInput.java --> add(new EqualInputValidator(formComponentLeft, formComponentRight, "SomeUserKey")); Regardsm -- Bruno Borges [EMAIL PROTECTED] Sun Certified Java Programmer for 1.4 Sun Certified Web Component Developer for 1.4
------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
