you can toggle the state with setenabled(true/false) inside onconfigure() method
-igor On Thu, Oct 7, 2010 at 1:10 AM, splitshade <martin.dil...@googlemail.com> wrote: > > Hi All!, > > we have a Problem here. > We have a Page, where lots of Panels are added. > These Panels should be individually enabled, as soon as a ValidationError is > available for one of them. > We have overridden isEnabled() for all Panels to return true, whenever an > Errormessage is registered for a Panel or one of its subcomponents (using > Visitor). > > > Enablement works like a charm, Problem is, that isEnabled is called before > FormValidation takes process, so in the first place, the panel and its > subcomponents are not validated, and as last call, isEnabled is called again > to check, if the panel should be displayed as Enabled. > > So, is this a bad design? would you solve it this way or is there even a > better solution i did not think of? > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Enable-FormFields-on-Error-tp2966341p2966341.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
