I believe the reason that the Validator errors are missing is that
Validator keys the errors with the property name of the form field.
And so, if you say that just show the errors whose property is
"ActionErrors.GLOBAL_ERROR" you would definitely miss out on the
Validator errors. It has nothing to do with the usage of the
deprecated ActionError and I believe you would still run in to this
problem even if you use ActionMessage
There are two options.
1) Extend html:messages to shown messages for all but a given property
2)
In the JSP you would follow the following steps
ActionErrors actionErrors = (ActionErrors)
RequestUtils.getInstance().getActionErrors(pageContext,
Globals.ERROR_KEY);
Iterator errors = actionErrors.properties();
pageContext.setAttribute("errors", errors);
<logic:iterate id="property" name="errors">
<logic:notEqual name="property"
value="<%=RIGHT_PANE_THRESHOLD_PROPERTY%>" type="java.lang.String">
<div class="errorMsg"><ul>
<html:messages id="message" message="false"
property="<%=property%>">
<li><bean:write name="message"/></li>
</html:messages>
</ul></div>
</logic:notEqual>
</logic:iterate>
Basically, you would be iterating over all the properties and showing
the errors to all but the property that you don't want to show the
errors for. [Note: one thing to note would be, I don't know if the
ordering of the errors will be the same of that you would get if you
leave the iteration to the html:messages.]
On 8/15/05, Chris Loschen <[EMAIL PROTECTED]> wrote:
> Does anyone have some ideas for me? Thank you!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
