[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1195.
------------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.10-core
1.2.10-core
I saw the problem in 1.2.9;
this is not a problem in 1.2.10
> Length validator broken if "maximum" attributes is missing
> ----------------------------------------------------------
>
> Key: TRINIDAD-1195
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1195
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.2.9-core
> Reporter: Stephen Friedrich
> Assignee: Matthias Weßendorf
> Fix For: 1.2.10-core, 1.0.10-core
>
> Attachments: 0-or-more-not-fewer.png, 2-up-to-a-maximum-of-0.png,
> confused.PNG
>
>
> <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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
