That case should not be done with required in my eyes, thats a data check that should have a specific value (true in this case). So thats an other data validator (just like range validator for a number)
On 1/8/08, Sam Barnum <[EMAIL PROTECTED]> wrote: > Right, like for an "accept terms" checkbox after some legalese stuff, > for example. > > On Jan 7, 2008, at 5:09 PM, Kent Tong wrote: > > > > > > > > > Dan Kaplan-3 wrote: > >> > >> But another way to look at it is this: When a checkbox is > >> unchecked, it > >> has > >> a value of "unchecked". Therefore, if you setRequired=true on a > >> checkbox, > >> it's always satisfied. In otherwords, a checkbox always has a > >> value so > >> setRequired=true has no effect on a checkbox. > >> > > > > Yeah, that's exactly the correct behavior in my mind. > > > > > > ----- > > -- > > Kent Tong > > Wicket tutorials freely available at http://www.agileskills2.org/EWDW > > Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA > > -- > > View this message in context: http://www.nabble.com/%22required%22- > > for-Checkbox-tp14662131p14680214.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
