You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2013/08/29 20:45:11 UTC
[jira] [Created] (TAP5-2164) Bean validation doesn't work when just
min, not max, defined in @Size
Thiago H. de Paula Figueiredo created TAP5-2164:
---------------------------------------------------
Summary: Bean validation doesn't work when just min, not max, defined in @Size
Key: TAP5-2164
URL: https://issues.apache.org/jira/browse/TAP5-2164
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-beanvalidator
Affects Versions: 5.4
Reporter: Thiago H. de Paula Figueiredo
If you use @Size defining without defining the max attribute, the max validation isn't added, but the data-range-max isn't added and the call to rangeValue(element, "data-range-max", Number.MAX_VALUE) ends up returning NaN instead of Number.MAX_VALUE and the value is always considered invalid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira