> so if you made this mistake imagine everyone else making it! Like I said, it was a mistake without real consequences, as the thing that is important here - making the embedded text field do the check - got done.
> > I'd also like to point out that this bug only had an effect when > > clients would call isRequired themselves, as for Wicket's functioning > > it's not really relevant. And making the isRequired function final is > > really to force people to use setRequired. > > > isrequired is a pretty common method to call. formcomponentlabels that add a > * for required components comes to mind immediately. Common for FormComponentPanels? Nah. Eelco
