Sorry to break your code. Good news is that you found a bug! Only
components that are visible should be validated anyway, as there is no
supported way that non-visble components could have delivered new data.
Besides the ineffiency, it might even lead to wrong results (e.g. a form
component with a required validator coupled would fail even though there
would be no chance to even deliver any value to that component). So...
I'm making the visibility check part of the validation now.
Eelco
Phil Kulak wrote:
Getting rid of IFormValidationStrategy will actually break some of my
code. I created a ValidateVisiableComponents strategy for when I have
many fields, but only a couple are visible (editing individual rows of
a ListView).
However, the rest of it sounds great (can't see it in CVS quite yet).
This was really due for a reworking and I'm glad that it will be in
the 1.1 release.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
