Carl,

This addresses a question that comes up on this list from time to time and
knowing some of the people at Zenika you have probably developed this with,
I am sure it will be a well thought out, robust and useful tool. It
hopefully also gives us a pretext on which to get you over to London again
for another talk at one of our upcoming London Wicket events!

In terms of the actual validation, have you given any thought yet to how
this can be done as DRY as possible wrt respecifying (equivalent/similar)
validation at various layers including Wicket's, the ORM's, in business
rules etc? 

Regards - Cemal
http://www.jWeekend.co.uk jWeekend 



cazoury wrote:
> 
> Hi,
> 
> We have been working on a small project to integrate 
> http://yav.sourceforge.net/ YAV  library with Wicket. It is javascript
> validation purely on the client side. YAV has a LGPL licence and is a
> sourceforge project.
> 
> I know that we can use an Ajax Behavior to validate the form with the
> validators present on the server side, but this is to respond to one of
> our client needs and also to illustrate how easy it is to integrate an
> existing javascript library with Wicket.
> 
> It has also some nice features like using in the javascript validation the
> same messages as the ones used by the Wicket application (default messages
> and user defined messages)
> 
> We would like to contribute, if possible, this code (wicket-contrib /
> wicket-stuff) if people finds this interesting. But I am not sure what are
> the different steps for that.
> 
> We where thinking making it a sourceforge or googlecode project, maybe it
> is the first step and then I could post the link to it on this forum.
> 
> Everyone enjoy the last day(s) of this year :)
> 
> Carl Azoury
> 

-- 
View this message in context: 
http://www.nabble.com/Contributing-to-Wicket---Client-side-form-validation-tp21219136p21219589.html
Sent from the Wicket - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to