--- On Tue, 9/16/08, Niall Pemberton wrote: > IMO the commons validator javascript is pretty horrible - > each validator assumes there is a method named after the > form which returns an array [...]
The original issue wasn't the JavaScript validation code itself, it was the inability to plug in *additional* custom client-side validations. There's no way to tie server-side validation configuration to client-side JavaScript methods (that I know of). My goal was simply to provide a way to define JavaScript validations on a page-by-page basis and have the existing validation code look for, and call, those validations if any were detected. I just want a stop-gap measure to provide an easy answer to the common need of adding different client-side validations to "fill the void" between now and whenever/ifever the existing XWork validation framework is revamped to provide this kind of functionality. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
