[jira] Commented: (TRINIDAD-1195) Length validator broken if "maximum" attributes is missing

["Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625993#action_12625993 ] 

Matthias Weßendorf commented on TRINIDAD-1195:
----------------------------------------------

Tested this (in JSPX):
<tr:inputText>
  <tr:validateLength minimum="2"/> 
</tr:inputText>

(default setting is that client side is turned on)

with 1.2.x trunk (1.2.10-SNAPSHOT)
entered "ABCDEF" ==> FINE (as expected)
entered "A" => ERROR (as expected)


I know you are using seam. Is it possible that some JAR (like Trinidad) overrides the id's for the validators?
Trinidad's tag creates the Validator (and the converter) based on the ID.

> 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
>         Attachments: 0-or-more-not-fewer.png, 2-up-to-a-maximum-of-0.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.