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.cgi?id=29679>. 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=29679 Validator returns ActionErrors instead of ActionMessages ------- Additional Comments From [EMAIL PROTECTED] 2004-06-18 19:38 ------- No, I'm not calling form.validate() in my action. I'm saying that the framework takes the ActionErrors instance that form.validate () returns and >magic happens< that results in the ActionErrors needing to be displayed in the JSP in the SAME WAY as if I had called the deprecated .saveErrors(ActionErrors) in my action. Since in my Actions I am supposed to use .saveMessages(ActionErrors), I now need to write two different JSP snippets. 1) A snippet with message="true" defined to catch my "savedMessages", and 2) A snippet without message="true" defined so as to catch the form.validate/validator "errors". I suppose it is good that the JSP can tell the types of errors apart, but should it really be incumbent on me to catch them both separately if I hadn't before...at least not without a deprecation warning of some kind? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
