You can create a validator decorator that does caching however you want -igor
On Aug 14, 2010 9:16 AM, "Martin Makundi" < martin.maku...@koodaripalvelut.com> wrote: Hi! Is it a necessary feature that validation occurs on components whose values have not changed? We have quite heavy validation criteria so it would be nice to optimize initializing the validator only for cases where component value has actually changed. We can do this with !getModelComparator().compare(this, convertedInput) but maybe this should be default behavior? Good reasons why not? Unchanged values are not anyways updated to model so why should they be validated.. just in case if validation criteria has changed since previous submit? ** Martin --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
