Hi! It might (and does) depend on other form component values.
** Martin 2010/8/15 Jeremy Thomerson <jer...@wickettraining.com>: > Why should the validation value be able to change? Why should it be a > moving target? > > On Sat, Aug 14, 2010 at 11:29 PM, Martin Makundi < > martin.maku...@koodaripalvelut.com> wrote: > >> Maybe MaximumValidator should take IModel? Why validators don't comply >> to the general pattern of using IModel...? >> >> ** >> Martin >> >> 2010/8/15 Igor Vaynberg <igor.vaynb...@gmail.com>: >> > the decorator just does the caching you want, tweaking the validators >> > is left up to you. >> > >> > -igor >> > >> > On Sat, Aug 14, 2010 at 11:58 AM, Martin Makundi >> > <martin.maku...@koodaripalvelut.com> wrote: >> >> Ok. That's pretty much same as my inline override. Is there a way to >> >> adjust mini/max value on the fly? >> >> >> >> ** >> >> Martin >> >> >> >> 2010/8/14 Igor Vaynberg <igor.vaynb...@gmail.com>: >> >>> it would mean add(new CachingDecorator(new MinimumValidator())); >> >>> >> >>> -igor >> >>> >> >>> On Sat, Aug 14, 2010 at 11:28 AM, Martin Makundi >> >>> <martin.maku...@koodaripalvelut.com> wrote: >> >>>> Thankx igor, what do you mean validator decorator? I am working on >> >>>> overriding MaximumValidator which practically means re-implementing it >> >>>> because the maximum value annot be changed on the fly. Decorator >> >>>> sounds nice...what would it mean in the case of >> >>>> Minimum/MaximumValidator or equivalent? >> >>>> >> >>>> ** >> >>>> Martin >> >>>> >> >>>> 2010/8/14 Igor Vaynberg <igor.vaynb...@gmail.com>: >> >>>>> 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 >> >>>>> >> >>>> >> >>>> --------------------------------------------------------------------- >> >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >>>> For additional commands, e-mail: users-h...@wicket.apache.org >> >>>> >> >>>> >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >>> For additional commands, e-mail: users-h...@wicket.apache.org >> >>> >> >>> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> > For additional commands, e-mail: users-h...@wicket.apache.org >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- > Jeremy Thomerson > http://www.wickettraining.com > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
