[TRINIDAD-1195] Length validator broken if "maximum" attributes is missing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.9-core
• Fix Version/s: 1.2.10-core, 1.0.10-core
• Assignee: Matthias Wessendorf
• Reporter: Stephen Friedrich
• Created: 26/Aug/08 20:39
• Updated: 27/Jan/10 08:45
• Resolved: 27/Aug/08 13:52

Description

<tr:validateLength minimum="2">

Client side validation always results in "Enter 2 or more characters, up to a maximum of 0."
No valid data can be entered at all.

Server side validation works in principal, but spits out an incorrect message when the validation (correctly) fails: "Enter 0 or more characters, not fewer."

See https://issues.apache.org/jira/browse/TRINIDAD-1130 for test.war that you can simply drop into Tomcat 6.

Much of my code omits the "maximum" attribute, because I have a maximum length set on my input components (so that joe user just cannot enter more characters anyway) and have wrapped the form in a seam validation (s:validateAll) that validates on the server side against constraints set with hibernate validation annotations on the entity objects (so that a hacker can do no harm).