how would specific components opt out? if i have a textarea i am going to add tinymce behavior to, i dont want it to be validated via ajax.
i often have validators that hit the database to check for uniquness, etc. since every time i press a key the entire form is reprocessed, it will add quiet a bit of overhead both to my database and to the response time of the ajax - because optimally if the field is standalone only that one field would be validated... -igor On Jan 27, 2008 8:04 AM, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > out of curiosity, would there be any interest in shipping Wicket with > Ajax form validation turned on *by default* instead of developers > manually adding the AjaxFormValidatingBehavior? Are there any > drawbacks to having this be the default behavior? > > > On Jan 27, 2008 9:00 AM, Ryan Sonnek <[EMAIL PROTECTED]> wrote: > > http://www.jroller.com/wireframe/entry/wicket_client_side_validation > > > > I've spent the past couple weeks investigating Wicket's support for > > client side validation. IMO, using Ajax for validation in Wicket is > > really amazing. Lots of folks are touting "javascript validation" > > right now, but I think Wicket has a definite advantage because the > > Ajax validation *reuses* all of your server side validation for free! > > This might be worth mentioning on the feature list somewhere and I'd > > be interested in any comments. > > > > Ryan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]