I'm not sure I know what to say here. Is Struts 1.2.1 really going to ship with a validator that does not maintain backwards compatibility with Struts 1.1?
Should I just go ahead an enter a separate bug for the js function naming issue? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 24, 2004 12:09 AM > To: [EMAIL PROTECTED] > Subject: DO NOT REPLY [Bug 29004] - ActionValidatorForms > cause badly formed validator javascript > > > DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG > RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT > <http://issues.apache.org/bugzilla/show_bug.cg> i?id=29004>. > > ANY REPLY MADE TO THIS MESSAGE WILL NOT BE > COLLECTED AND > INSERTED IN THE BUG DATABASE. > http://issues.apache.org/bugzilla/show_bug.cgi?id=29004 ActionValidatorForms cause badly formed validator javascript ------- Additional Comments From [EMAIL PROTECTED] 2004-06-24 04:09 ------- The struts-examples web application exhibits this problem. In particular, the registrationForm was tested for this. Trying to track down the cause, it seems after ValidatorResources loads the streams through the plugin, the args in the form fields have no data. The unit tests in commons-validator do not leave empty args and can't quite figure that out just yet. --------------------------------------------------------------------- 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]
