or instead,
maybe make that hibernatevalidator also be a behavior, and simply toggle
component's setrequired in onattach
-igor
On 6/19/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
i dont know about that. isvalid's contract is that it only returns false
if there are error messages reported against the component.
i think this would be simple enough
class hibernatetextfield extends textfield {
valid() {
if (hibernaterequired()) {
if (Strings.isEmpty(getInput()[0])) {
error(new ValidationError().addMessageKey("Required"));
return;
}
}
super.validate();
}
-igor
On 6/19/07, Jan Vermeulen <[EMAIL PROTECTED] > wrote:
>
>
>
> igor.vaynberg wrote:
> >
> > i would not be against making formcomponent.validate() non-final
> >
> > -igor
> >
>
> I was thinking of making 'isValid()' non-final, and adding that logic in
> there.
>
> Jan.
> --
> View this message in context:
>
http://www.nabble.com/Problem-with-latest-changes-in-FormComponent%3Avalidate%28%29-tf3945885.html#a11200420
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>
