DO NOT REPLY [Bug 17129] New: - Validator Feature Request

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17129>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17129

Validator Feature Request

           Summary: Validator Feature Request
           Product: Struts
           Version: 1.1 Beta 3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Validator Framework
        AssignedTo: struts-dev@jakarta.apache.org
        ReportedBy: jfarley@studentadvantage.com


Hopefully this is the proper forum for requesting features.  The 
<html:errors ... /> tag is more geared towards presenting a full list of errors 
to the user at the top of the page.  My business opted instead to display 
individual error messages above each input field (which we implemented with a 
combination of logic:messagesPresent and html:errors tags).  However, this 
solution also requires an error "lead-in" and (sometimes) a "lead-out" that 
says something like "Please check the fields below for errors".  The only way I 
could find to implement this functionality is by extending the ValidatorForm 
and checking to see if the ActionErrors collection has a size > 0 and, if so, 
including a couple extra errors.

To solve this problem, it would be handy to be able to define in some manner 
errors that are included if another field failed validation.  So you could 
define a lead-in and lead-out error that would get included if any field of 
that form failed validation.

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org