On 8/15/07, Matej Knopp <[EMAIL PROTECTED]> wrote: > We never override isRequired in Wicket. So we keep the contract of > setRequired. But we shouldn't prevent users to override it. If user > wants to break the set contract, it's ok. I don't see anything bad > about it.
But do you see anything bad about users overriding setRequired? Which is why this thread was started... Eelco
