[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626480#action_12626480
]
Stephen Friedrich commented on TRINIDAD-1195:
---------------------------------------------
> entered "1" and got an error (as expected)
Yes, but please do have a close look at the screenshot "server-side1.PNG" you
uploaded yourself.
It shows exactly the problem that I mentioned right from the start:
"Server side validation works in principal, but spits out an incorrect message
when the validation (correctly) fails: "Enter 0 or more characters, not fewer.""
You might just as well call that message funny or stupid, but it will
definitely confuse users when they are told not to enter fewer than zero
characters.
> I noticed it has changed (the required is removed, when clicking the
> checkbox)
Yes, the icon is removed, but _try to submit_ with an empty value and
validation fails and tells you you must enter a value.
> 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, server-side1.PNG, server-side2.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.
