commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15396] - Indexed properties not being set in ValidatorResults
Date Mon, 16 Dec 2002 20:58:12 GMT
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=15396>.
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=15396

Indexed properties not being set in ValidatorResults





------- Additional Comments From turner@blackbear.com  2002-12-16 20:58 -------

I'm not so sure that this is a bug.  In most cases, an indexed property is 
going to be used in a table-style of input with an iterator.  You wouldn't 
want to display each error on the line, you'd display them at the top.  If we 
went to storing indexed property error messages on the full property with 
index, you'd need to put an iterator around bean:errors in Struts (for 
example) to generate all the error messages.

Willing to hear counter arguments.

James

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message