see my previous mail (i aksed the same thing to eelco)
> just don't add the behavior to the behaviors
> just in render also walk over the validators and get the behavior if it
> has
> one.
> then if you remove the validator everything is gone.
but where do you keep the reference? if you create a new one on every
request then these behaviors cant have state!
getBehaviour shouldn't return everytime a new one
just the same thing. (it could be a new one if he wants thats up to the
validator)
but i see other problems comming because if validators also add stuff to the
> tag
> like onchange or onblur. Then what happens to the other behaviors (maybe
> ajax)
> that also wants to do something?
this is a problem even now. basically we need to be careful and merge
attributes instead of simply setting them (overwriting whatever was there
before)
yeah but they are comming to bite us much much harder with client side
validation
people expect that when validation fails there rest is not called.
so on the client side it must be a thing we do specific for validators
You really don't want developers to merge that them selfs
how can they do that with all the standard (ajax) behaviors we have now??
If i attach a validator to a field (Range) that has clientside also build in
(on onchange)
and i also want a FormComponenUpdatingBehavior on it (on onchange)
then those should 'merge' automatically but the validator should go first
and if it fails the other behaviors shouldn't be called but only if it is ok
the form component
updating behavior should work.
johan
