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
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place."
- Carlos Santana
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
