Hi,
Interesting approach. I don't think we'll support this out of the
box, as
it is very basic, and your approach is very easy to implement by other
users.
hmm, I think the approach of having no messages by default could be
more suitable, because the default messages will (if I get it right)
show the internal id which could be not very helpful to the user
(because the label before the form component could be entirely
different). Maybe Wicket shouldn't support highlighting form fields
using css classes but it should provide a way to plug-in behaviour
for showing validation results on per-form basis. If you want to do
the little asterisks for showing invalid input (like in the wicket
examples), you have to add a panel around every form component which
is just a lot of code/markup for a little detail that could be
expressed once when creating the form...
If you don't mind, I've created a wiki page with your description
for your usecase.
No problem at all with that; although I'm not sure if my code is
written well-enough for general usage (I was very solution focused
when writing this) - I'm especially unsure about adding the
AttributeModifier in the onBeginRequest method of the form...
Regards,
Ralf
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
