JSF 2 – Bean Validation: validation failed -> empty values are replaced with last valid values from managed bean

by

Your particular problem is caused by

<context-param>
    <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name>
    <param-value>true</param-value>
</context-param>

and a bug (at least, an oversight) in HtmlBasicRenderer#getCurrentValue() of Mojarra:

if (component instanceof UIInput) {
    Object submittedValue = ((UIInput) component).getSubmittedValue();
    if (submittedValue != null) {
        // value may not be a String...
        return submittedValue.toString();
    }
}

String currentValue = null;
Object currentObj = getValue(component);
if (currentObj != null) {
    currentValue = getFormattedValue(context, component, currentObj);
}
return currentValue;

Normally, the submitted value is set to null when the UIInput component is successfully converted and validated. When JSF is about to redisplay the value, it first checks if the submitted value is not null before proceeding to redisplay the model value. However, with this context parameter, it is null instead of an empty string when it is invalid and thus it will always redisplay the original model value when you remove the initial value of a required field.

To test it, set that context param value to false or remove it altogether. You’ll see that it works as intended. However, it will bring back the disadvantage that your model values will be cluttered with empty strings on empty but non-required fields and you’ll lose the advantage of using @NotNull annotation of JSR 303 bean validation.

To fix this, you’ve to alter the first part of HtmlBasicRenderer#getCurrentValue() as follows:

if (component instanceof UIInput && !((UIInput) component).isValid()) {
    Object submittedValue = ((UIInput) component).getSubmittedValue();
    if (submittedValue != null) {
        // value may not be a String...
        return submittedValue.toString();
    } else {
        return null;
    }
}

I’ve already reported it to Mojarra guys as issue 2266.

More Related Contents:

  1. Validating input using java.util.Scanner [duplicate]
  2. Migrating from JSF 1.2 to JSF 2.0
  3. How to use Scanner to accept only valid int as input
  4. Struts2 INPUT result: how does it work? How are conversion / validation errors handled?
  5. Spring MVC: How to perform validation?
  6. How can I check if a single character appears in a string?
  7. Recommended JSF 2.0 CRUD frameworks [closed]
  8. How to mark JTable cell input as invalid?
  9. JSR 303 Validation, If one field equals “something”, then these other fields should not be null
  10. How to check whether a given string is valid JSON in Java
  11. JSF convertDateTime renders the previous day
  12. Difference between @Valid and @Validated in Spring
  13. i18n with UTF-8 encoded properties files in JSF 2.0 application
  14. Validation of a list of objects in Spring
  15. Is there a way in Java to determine if a path is valid without attempting to create a file?
  16. How to check for a valid URL in Java?
  17. Java Regex to Validate Full Name allow only Spaces and Letters
  18. Get current page programmatically
  19. Validate an XML file against local DTD file with Java
  20. Is there an implementation of JSR-303 (bean validation) available?
  21. Unique constraint with JPA and Bean Validation
  22. How to reference JSF managed beans which are provided in a JAR file?
  23. Manually call Spring Annotation Validation
  24. Validating IPv4 string in Java
  25. XML syntax validation in Java [closed]
  26. How to validate XML against XSD 1.1 in Java?
  27. Regex date validation for yyyy-mm-dd [duplicate]
  28. Check Credit Card Validity using Luhn Algorithm
  29. @EJB in @ViewScoped managed bean causes java.io.NotSerializableException
  30. Prevent accessing restricted page without login in Jsf2

Leave a Comment