Hi, in my opinion - and small experience, I had not difficulties when switching to the Validator.
The only things I had to do were: - removing validateXXX() method, XXX being a (set of) field in my form - adding the right rules in my validation.xml Where you might get in trouble is that validator rules may not be as accurate as your validateXXX() methods... (further programming is required). Another thing I dont like in Struts Validator is that <html:errors/> translation comes preformatted (error title is not i18N compliant, encapsulated in <h3>..</h3> and with an ugly <hr/>): you loose the ability of putting a well displayed error beside each field of your form (this is not the case if you use Javascript Validator facility). Coming back to your question, you generally won't have any difficulties when switching from ActionForm validation to Validator implementation and it's really a convenient way to share pattern matching design between several forms... Vince -----Original Message----- From: Susan Bradeen [mailto:SusanB@;softlanding.com] Sent: Thursday, October 24, 2002 7:50 PM To: [EMAIL PROTECTED] Subject: Validator later rather than sooner? Is it general practice, or recommended, to develop a Struts application using the Action/ActionForm classes first (getting everything working properly) and later switch to the Validator classes, OR to use the Validator classes (implementing validation) right from the beginning? I have done a little with form validation, but not enough to know if I will get myself in trouble by waiting and "switching" class sets later on. Thanks, Susan Bradeen -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
