Joe writes: >>Otherwise, Paul, I'm not sure what you mean... is your idea that an XMLHttpRequest call would be made to do server-side validation for each form update? The overhead is likely to make that an impractical solution. Or are you wondering how errors would be reported back to the page as a response from an XMLHttpRequest?
I am not quite sure why "the overhead makes it impractical," unless there is a physical barrier such as bandwidth restraint -- but that sounds like a case-by-case decision is required. But I've seen some forms, which I think AJAX runs behind the scenes to do validation. (If I can re-find a link I will send it.) When a non-date field is entered into a date field, for instance, an error message is shown to its side. This client-side reporting is akin to the errorStyles, which were added to the Struts 1.2.5 tags to allow per-field reporting on the server-side. -----Original Message----- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, April 18, 2005 1:38 PM To: 'Struts Users Mailing List' Subject: RE: AJAX: Whoa, Nellie! At 11:15 AM -0400 4/18/05, Benedict, Paul C wrote: >Frank, will Ajax support be tied into reporting form errors? It would be >interesting to break down the validator into individual validations, so >errors can be reported to the user as he types. Independent of Ajax, Niall Pemberton has done a substantial overhaul of commons-validator which will support per-field validation instead of only onsubmit. http://www.niallp.pwp.blueyonder.co.uk/validatorjs.html It's really quite impressive, and I think it's only pending Niall having enough time to really give it a good run-through, since it's a pretty big change. Otherwise, Paul, I'm not sure what you mean... is your idea that an XMLHttpRequest call would be made to do server-side validation for each form update? The overhead is likely to make that an impractical solution. Or are you wondering how errors would be reported back to the page as a response from an XMLHttpRequest? I don't think this is part of Frank's kit (sorry if it is and I missed it) but it makes sense from a framework standpoint to have standard XML representations of Struts concepts (like ActionMessages) paired with a JavaScript library that can convert those into a standardized JavaScript object model. I haven't tried yet to solve any problems with Ajax where this would be useful, but it's definitely the kind of thing you wouldn't want to leave each person to have to rewrite him- or herself. Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. ------------------------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
