[EMAIL PROTECTED] wrote:
I'm not so sure about using different style for front end and back end
errors - great for a developer but confusing for a user (of a consumer
site)
I display form errors within the form itself (with a non-radical message
saying they screwed up) and system errors in
...
system-oriented error types never run.
Dave
When I was using an older version of Struts I used ActionErrors and I could
get away with just one set of jsp tags. I guess they have been deprecated
for a good reason.
Anyhow, when I get time I'll move the validation from my action class t
[EMAIL PROTECTED] wrote:
Thanks Dave that worked... my errors.jsp is pasted below. So I used
two sets of tags one for the struts validation errors and one for the
action errors. It would have been more elegant using only 1 set of
tags but I guess this works just fine.
That's actually what I
Thanks Dave that worked... my errors.jsp is pasted below. So I used two sets
of tags one for the struts validation errors and one for the action errors.
It would have been more elegant using only 1 set of tags but I guess this
works just fine.
<%@ page contentType="text/html;charset=UTF-8" la
[EMAIL PROTECTED] wrote:
Errors are displayed as I expect through my validation.xml but no
error is displayed when it goes through my action class. Any ideas why?
protected ActionForward errorToInput(final HttpServletRequest
request_, final ActionMapping mapping_, final String errorKey_, f
user@struts.apache.org,
I have a validate() method on my form bean which returns ActionMessages, I
call the method from my action class. In my logs I can see that
ActionMessages have been populated and the flow is redirected to my error
page.
My validation method is:
public ActionMessages
6 matches
Mail list logo
