ActionError has been deprecated for some time so we could remove it in 1.3. ActionErrors only exists because of ActionForm.validate(). I figured we would remove ActionErrors, ActionMessages, and ActionMessage in 2.0 and replace them with commons-resources.
I wouldn't be opposed to deprecating ActionErrors and changing the ActionForm.validate() signature to return ActionMessages in the 1.x series though. Seems like it would reduce confusion even if it's a minor API breakage. David --- Ted Husted <[EMAIL PROTECTED]> wrote: > On Fri, 29 Oct 2004 08:35:11 -0500, Joe Germuska wrote: > > This may be Ted's question asked in different words. > > My question in different words :) is: > > What is the roadmap for ActionMessage/ActionMessages and > ActionError/ActionErrors for 1.3 and beyond? > > The endgame has been to migrate to Commons Resources, so people could > use the same classes in the backend and pass them directly out to > Struts. > > * http://jakarta.apache.org/commons/sandbox/resources/ > > But we have to bring it up from the sandbox first. > > I'd imagine that any message handling support for Shale would also be > based on Commons Resources. > > -Ted. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
