[jira] Resolved: (WW-1191) JavaScript validation (non-Ajax) doesn't look for an existing message before adding a new validation error

["Don Brown (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/struts/browse/WW-1191?page=all ]

Don Brown resolved WW-1191.
---------------------------

    Resolution: Fixed
      Assignee: Don Brown  (was: Rainer Hermanns)

I can't replicate this problem, even with the mailreader application to which Ted is referring.  If someone can describe how to reproduce this, please reopen.

> JavaScript validation (non-Ajax) doesn't look for an existing message before adding a new validation error
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: WW-1191
>                 URL: http://issues.apache.org/struts/browse/WW-1191
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Misc
>    Affects Versions: WW 2.2.1
>            Reporter: Matt Raible
>         Assigned To: Don Brown
>             Fix For: 2.0.0
>
>
> If I have a last name field that's required:
> 1. When I hit submit, I get an error above the field like expected.
> 2. If I hit submit again (w/o filling in the last name), I end up with two messages:
> Last Name is required.
> Last Name is required.
> If I look at the rendered code, it looks easy to fix:
> <tr errorfor="saveUser_user_lastName">
> <td colspan="2" align="center">
> <span classname="errorMessage" class="errorMessage"> Last Name is required. </span>
> </td>
> </tr>
> Obviously "errorfor" and "classname" are invalid attributes, but you should still be able to look for them before adding a new message.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira