Shahid N. Shah wrote:
Eelco,
Can you elaborate how validation in your new scheme will work for invisible
components? Right now it seems to be a "bug" that invisible components are
validated. Do you agree? If you do not agree, can you elaborate why it might
be good to validate invisible components? For instance, if a field is
required normally but for a particular reason it is made invisible the
NotNull validator still runs.
You're absolutely right! Thanks for finding it too.
One remark to all readers: please, if you stumble on things that makes
using Wicket awkward in any way, please share it! It might be a bug like
this case, or at least it points to an area that could be improved.
Cheers,
Eelco
Right now whenever we add a validator we try and check for the invisibility
flag but putting that code check everywhere is getting a bit tedious :-).
Thanks for all your hard work!
Satisfied Wicket user,
Shahid.
-
-------------------------------------------------------
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
