[
https://issues.apache.org/jira/browse/TRINIDAD-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626109#action_12626109
]
Matthias Weßendorf commented on TRINIDAD-1195:
----------------------------------------------
I am sorry to say, that I am still (not used your app) able to get the error
with the latest greatest Trinidad 1.2.10-SNAPSHOT.
Did a check out of this:
https://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/
did the build => mvn install
started the trinidad-demo, using JSF RI 1.2_09
cd trinidad-examples/trinidad-demo
mvn -PjettyConfig -Djsf=ri jetty:run
My page is pretty simple:
<?xml version="1.0" encoding="iso-8859-1" standalone="yes" ?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page"; version="2.0"
xmlns:f="http://java.sun.com/jsf/core";
xmlns:tr="http://myfaces.apache.org/trinidad"; >
<jsp:directive.page contentType="text/html;charset=utf-8"/>
<f:view>
<tr:document title="Apache Trinidad Demo Index">
<tr:form>
<tr:panelFormLayout>
<tr:inputText>
<tr:validateLength minimum="2"/>
</tr:inputText>
<tr:commandButton text="Go" />
</tr:panelFormLayout>
</tr:form>
</tr:document>
</f:view>
</jsp:root>
Next step is checking your WAR w/ updated JARs.
> 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.
