You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2004/12/17 03:08:46 UTC
DO NOT REPLY [Bug 22046] -
[validator] Field validation for a list of fields
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=22046>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=22046
------- Additional Comments From sclementi@wi.rr.com 2004-12-17 03:08 -------
Created an attachment (id=13768)
--> (http://issues.apache.org/bugzilla/attachment.cgi?id=13768&action=view)
Patch allowing for validation of all elements in an indexed property or current
behavior
This addresses this issue as well as part of 16394.
The property isValidateAllElements is introduced on the Field class. This
property controls whether validation of indexed properties should be performed
for all list elements or stop upon the first invalid element (current and
default behavior). If the this property is set to true, the ValidatorResults
for an indexed property are keyed such that the index is included. I.e. given a
field with property = 'a' and indexListProperty = 'list', a validation failing
on the 10th element would appear in the ValidatorResults with the key
list[9].a
FieldTest and ValidatorActionTest have been updated accordingly.
I am not aware of any incompatibilities introduced by this patch. All current
code should still operate as is as the default behavior is unchanged.
The only open issue I see is that the dtd does not support the new property
(even though Digester is kind enough to load it up anyway).
(Please note that there are many test failures, these were failing before I got
here :<( )
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org