I used to add custom FormValidators to forms where multi-field validation was required (like checking if two copies of an entered password match. However, this approach has some problems – I had to list the dependent components and if some of them were hidden at validation time, the validator didn’t work. Reading around, I saw the recommendation to use the onValidate() method of the form to do validation and this seems a lot more straightforward. Here’s a sample wicket form with some validation logic to check if the current password matches and if the two copies of the new password are the same. [code language=”java”] final Form form = new Form("form", new CompoundPropertyModel(user)) { private static final long serialVersionUID =[…]