[TAP5-2164] Bean validation doesn't work when just min, not max, defined in @Size

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 5.4
• Component/s: tapestry-beanvalidator
• Assignee: Unassigned
• Reporter: Thiago Henrique De Paula Figueiredo
• Created: 29/Aug/13 18:43
• Updated: 09/Sep/13 16:43
• Resolved: 09/Sep/13 16:43

Description

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.

Issue Links

• duplicates: TAP5-2158 Client-side validation of @Size is not working when only min or max is set