Thanks, that solved my problem.

As of what should be default, my suggestion is to let checkRequired return 
false because:

1. 1.3 now breaks existing code. Changing it right away will spare existing 
users from agony :)
2. A new user is likely to expect a "required-error" if he does 
setRequired(true) on a CheckBox.

-- Edvin

Igor Vaynberg skrev:
correct, but we need to figure out what the framework default should be.

i dont really have an inclination either way

-igor


On Jan 4, 2008 9:06 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Whatever the resolution, Edvin can override checkRequired on that
checkbox of his and return false as I understand it?

Martijn


On Jan 4, 2008 5:40 PM, Matej Knopp <[EMAIL PROTECTED]> wrote:
I'm not sure either. It can be convenient, when you have for example a
license agreement. Then you just call checkbox.setRequired(true) and
you're done. What are the cons?

-Matej


On Jan 4, 2008 5:33 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
hmm, that was actually a request:
https://issues.apache.org/jira/browse/WICKET-1221

not sure what to do here...

-igor



On Jan 4, 2008 7:49 AM, Edvin Syse <[EMAIL PROTECTED]> wrote:
I just filed: https://issues.apache.org/jira/browse/WICKET-1260

I'm on a deadline for a project and this makes it impossible for me to
deploy. Can anyone think of a workaround I could use in the meantime?

Sincerely,
Edvin Syse

---------------------------------------------------------------------
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]




--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0


---------------------------------------------------------------------
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]

Reply via email to