[TAP5-2158] Client-side validation of @Size is not working when only min or max is set

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.4
• Fix Version/s: 5.4
• Component/s: tapestry-beanvalidator
• Assignee: Thiago Henrique De Paula Figueiredo
• Reporter: Balázs Palcsó
• Created: 17/Aug/13 12:07
• Updated: 01/Nov/13 22:22
• Resolved: 01/Nov/13 20:18

Description

Exact version: 5.4-alpha-14

Server side example:

@Size(min = 3)
private String name;

On the client side the following function gets executed:

doRangeValidate = function(element, value, memo) {
      var max, min;

      min = rangeValue(element, "data-range-min", 0);
      max = rangeValue(element, "data-range-max", Number.MAX_VALUE);
      if (_.isString(value)) {
        value = value.length;
      }
      if (!((min <= value && value <= max))) {
        memo.error = (element.attribute("data-range-message")) || "RANGE ERROR";
        return false;
      }
      return true;
    };

In the above example max is evaluated to NaN and therefore the function returns false causing validation error.

Same applies when you only max is specified in @Size annotation and min is evaluated to NaN.

Workaround

Specify both min and max.

Issue Links

• is duplicated by: TAP5-2175 Bean Validation fails when @Size(min) is not specified but max is specified
• is duplicated by: TAP5-2164 Bean validation doesn't work when just min, not max, defined in @Size