You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Kent Tong <ke...@cpttm.org.mo> on 2007/06/25 03:46:44 UTC
Re: DropDownChoice spring cleaning
Martijn Dashorst <ma...@...> writes:
> All form components now have a method 'setRequired'. This tells
> whether the component must have a value != null (or empty string) or
> not. The DDC has a set of methods that deal with the same stuff:
> - isNullValid() / setNullValid(boolean nullValid)
>
> This can be replaced with 'isRequired/setRequired'. Any objections to
> deprecating them, replacing the contents with "return !isRequired();"
> and "setRequired(!nullValid)", and making them final?
Any decision on this? nullValid is still in 1.3-beta1. It is plain
confusing and really equivalent to (!required).