Joe Germuska wrote:
I agree, all I've done for myself is implement "saveError" and "saveMessage" methods which do this in my Action base class. So it could easily be something like an addition of these methods with a possible deprecation of saveErrors/Messages sometime over future versions.If I have errors occur in different locations, rather than returning ActionMessages objects and having to merge them myself prior to calling "saveErrors" or "saveMessages", why not have this be more like "addError" or "addMessage" at the action level so that the user doesn't need to maintain the "ActionMessages" object themselves? As well they can call saveError almost anywhere in the code without overwriting the existing errors object, which is "saveErrors" existing behavior.
I wouldn't object to having "addErrors" methods which do this, but I think it would be wrong to change the behavior of saveErrors to no longer remove existing messages. Same, of course, goes for addMessages/saveMessages
Joe
Mostly, I'm just presenting things I find useful while I'm working with the library.
-Mark
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
