--- Robert Leland <[EMAIL PROTECTED]> wrote:You're right. We could provide a stop gap ActionForm.validateToMsg() or whatever that returns a
I believe at one time we were going to deprecate ActionErrors since it is really a shell over ActionMessages. We could still keep the error tag, just make it use ActionMessages directly.
It would be nice to get rid of it but I don't think we can until 2.0. ActionForm.validate() (and other methods) return an ActionErrors object. There is no way to deprecate those methods with a new version that returns
ActionMessages because return types aren't part of method signatures. I
think this would break backwards compatibility but I would love to be
wrong on this one :-).
list of ActionMessages objects. We could then get rid of ActionError internally by making it a facade
of ActionMessage instead of extending ActionMessage. The same goes for ActionErrors, it would only be a facade.
and only created when needed.
Also, ActionError should be deprecated with ActionErrors because it's just a useless subclass of ActionMessage.
David
[ ] +1 Yes deprecate ActionErrors [ ] 0 Yes, but you'll have to face the angry crowds yourself. [ ] -1 No, and here is why.
-Rob
-- Robert Leland [EMAIL PROTECTED] ------------------------------------------ Java, J2EE, Struts, Web Application Development
804 N. Kenmore Street +01-703-525-3580 Arlington VA 22201
