You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@wicket.apache.org by Martin Makundi <ma...@koodaripalvelut.com> on 2011/04/22 10:52:32 UTC

MinimumValidator should have model?

Hi!

MinimumValidator should have model so that boundaries must be
initialized only for changed form components?

**
Martin

Re: MinimumValidator should have model?

Posted by Martin Makundi <ma...@koodaripalvelut.com>.

Yes, ofcourse, but it seems weird that the built-in wicket validators
don't follow the IModel pattern.

**
Martin

2011/4/22 Martin Grigorov <mg...@apache.org>:
> I don't understand the question but you can create your own IValidator
> that do exactly what you need.
>
> On Fri, Apr 22, 2011 at 11:52 AM, Martin Makundi
> <ma...@koodaripalvelut.com> wrote:
>> Hi!
>>
>> MinimumValidator should have model so that boundaries must be
>> initialized only for changed form components?
>>
>> **
>> Martin
>>
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>

Re: MinimumValidator should have model?

Posted by Martin Grigorov <mg...@apache.org>.

I don't understand the question but you can create your own IValidator
that do exactly what you need.

On Fri, Apr 22, 2011 at 11:52 AM, Martin Makundi
<ma...@koodaripalvelut.com> wrote:
> Hi!
>
> MinimumValidator should have model so that boundaries must be
> initialized only for changed form components?
>
> **
> Martin
>



-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com