Well, if you feel strongly about this, maybe it is time to open another discussion about this specifically or (maybe better as we're having to digest lots of traffic to start with) a JIRA feature request.
Eelco On 5/11/07, Bruno Borges <[EMAIL PROTECTED]> wrote:
Because Wicket is component based... :) We actually reuse components and somewhere we want to disable validators. For example: chained components where one component if selected, must disable another component's validator. -- Bruno Borges Summa Technologies Inc. www.summa-tech.com (48) 8404-1300 (11) 3055-2060 On 5/11/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > How about enabled/disabled validators (and their behaviors) ? This way, > no > > counting down is needed and when validatores are disabled, they > propagate > > this state to behaviors. Removing validators is strange to me, but > disabling > > them for a while, I think this is more reasonable. > > Maybe. Again would be more in line with behaviors. But now the million > dollar question: for what use case? When would you actually ever need > to remove or disable a validator? And *if* you would ever need such an > exotic case, why does Wicket have to do this for you and why don't we > tell people to just make this part of the way they implement their > validation method? > > Eelco >
