Comments on: User friendly form validation with Wicket

By: Mark

Mark — Fri, 05 Mar 2010 10:28:46 +0000

Sry for my last post – i just red the other comments and this solution works! Thanks!

By: Mark

Mark — Thu, 04 Mar 2010 09:06:59 +0000

Nice article!!
I have one question regarding validation with models which are direclty bound to hibernate entities. The problem i have if i use your component that wicket looks for getter/setter of the feedbacklabel which of course doesnt exists. Is there a elegant way to say wicket dont use the feedbacklabel for the model bound to the form? I am new to wicket so my question could be stupid .
Thanks for your help!

By: Björn

Björn — Tue, 16 Feb 2010 13:24:02 +0000

Hi there,
i tried using this FeedbackLabel with the ComponentVisualErrorBehavior.
But there is one thing I don’t understand:
while the field is invalid it shows me the correct Errormessage, but when I go back and correct the input to be valid, the error message doesn’t disappear. How do I make it delete it again? Since the onError(..) method is still called not even the style-class is set to “valid” Why could that be?
I’d appreciate some help, thanx in advance
Cheers Björn

By: Antoine

Antoine — Mon, 08 Feb 2010 15:56:04 +0000

Maybe I missed something – but why go to the trouble of creating a new component instead of using a feedback filter which is readily available in the Wicket framework?

Example:
FormComponent nameField = new RequiredTextField(”name”);
add(new FeedbackPanel(”nameFieldFeedback”, new ComponentFeedbackMessageFilter(nameField)));

That feedback panel will only show messages relevant to the nameField component, exactly what your FeedbackLabel component is doing.

By: Timo

Timo — Fri, 11 Dec 2009 07:43:12 +0000

Aargh… This kind of workarounds/extensions/whatever of frameworks just make me more unsure if Java is not a right tool create web applications. IMHO, things like these should be easily available in the framework itself…

By: Elad

Elad — Thu, 12 Nov 2009 18:52:03 +0000

If you want to use this in 1.4 you will need to change the setModel method to setDefaultModelObject as stated in the migration guide to 1.4

By: Track your running miles using Apache Wicket, GlassFish, NetBeans, MySQL, and YUI Charts « Miles to go …

Wed, 21 Oct 2009 15:52:28 +0000

[...] Form Validation & Default Error Handling: There are validators available to enable basic checking like required, number / pattern / range / date validator. Anything above that needs to be custom built and adds to the verbose nature of the framework. For example a "FormValidator" was built to support the validation for each elements of the form. Custom messages for each validation message can be displayed as explained here. More user-friendly messages can be displayed as explained here. [...]

By: Ala

Ala — Fri, 11 Sep 2009 13:40:23 +0000

We are doing something similar, but instead of having extra code (panels to show the error) for each field we just have a visitor that goes through the form and then adds a border/changes style class etc. to every component that failed validation. We also have a variant that dynamicly inserts the “feedback label” using dom manipulation and ajax, e.g. adding new component markup and the component dynamicly.

By: jim

jim — Sat, 16 May 2009 16:57:09 +0000

Can anyone think of a way to use taborder instead of onBlur? onBlur does not work for radiobuttons etc. Or maybe a way to add a wicket behavior to focus on the next element when the previous element is validated?

By: Daan

Daan — Thu, 23 Apr 2009 06:09:32 +0000

Hi Maarten,

These look indeed quite similar
Thanks for the link!

- Daan