mixing validators and behaviors has been on our todo list for a while, but we couldnt do it cleanly in 1.3 because it would mean an api break.
we will do it for 1.4 as far as getting the name of formcomponent, that is already possible through ibehavior.bind(component) -igor On Jan 27, 2008 12:07 PM, Flemming Boller <[EMAIL PROTECTED]> wrote: > Hi > > Just a thought about client side validation. > > I have looked at simple validation like maxlength, min length stuff like > that. The jQuery > validation plugin solves that easily. > > My idea was to inherit from the corresponding wicket-validator and implement > IBehavoir. > Then I would be able to generate javascript based on the validator. > > I would then add my "javascript-enabled-validator " to the form classes. > > Would that be a way to go? comments anyone? > > The problem I see is to get the name attribute from the formcomponent, > but I guess I have to look at the Javadoc for wicket > > /Flemming > > > > > On Jan 27, 2008 4:00 PM, 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]
