struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Lowe <>
Subject Re: Deprecated: ActionError
Date Tue, 13 Jan 2004 15:36:19 GMT
Sorry I don't usually post this group but is there actually a sensible 
replacement for action errors yet?

That messages stuff still falls short of offering the same level of 
slickness that action errors does, perhaps this is due to he 
html:errors tag but i personally and i imagine others all that 
messagesPresent nasty mess.

There's still no clear means of accessing a single property of the 
messages vector/array/list (whichever it is). I've asked this question 
a few times on the user list, but what exactly is the replacement for 
action errors and the accompanying tags.

<logic:messagesPresenet bla bla is disgusting and there's no obvious 
way to drill to the property in the common situation of wanting to 
display an error by a form element.

Sorry wont post again, but its a tad irritating that something this 
useful is being deprecated in favor of some rancid camel's jism of an 

  Cheers Mark

On 13 Jan 2004, at 14:15, Matthias Wessendorf wrote:

> Hi,
> i watched at the sources and figured out, that
> ActionError is deprecated so that i have to use ActionMessage. Okay.
> The add() in ActionErrors is also deprecated, because of first. fine.
> So i watched the Validator-Sources (class FieldChecks)
> i saw there ist ActionMessages in use for "errors".
> for the deliverd Methods.
> So i looked at our validate() in ActionForm,
> but there is still ActionErrors.
> So i wondered, why the validator uses Messages and
> the validate() uses Erros...
> and also i saw, that the validator gets
> initialized with an ActionErrors-object in:  Resources.initValidator();
> inside of initValidator()
> this happends:
> validator.setParameter(ACTION_ERRORS_PARAM, errors)
> but "key" for errors is this:
>     private static String ACTION_ERRORS_PARAM =
>         "org.apache.struts.action.ActionMessages";
> the first parameter of "setParameter()" is called: 
> "parameterClassName".
> so the errors gets initialized as an ActionMessages-object, isn´t?
> so question:
> why is the ActionErrors not deprecated?
> in release-notes i saw:
> "Although not removed, in many cases you should replace the deprecated
> ActionErrors with the preferred ActionMessages to ensure correct
> operation."
> why not in all?
> it would be fine, to know this ;-)
> greetings
> Matthias
> Matthias Weßendorf
> Email:
> URL:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message