When setting javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL to true, the old (or initial) model value is redisplayed on @NotNull validation error instead of the submitted value.
A required submitted value, which is afterwards removed and re-submitted, should not reappear.
This issue is reported in JAVASERVERFACES_SPEC_PUBLIC-671 and it's fixed in the revision 0813ee1fdef418e47ef03ced7d57a1abe4c2bf54. Please backport this to JBoss mojarra.
- clones
-
WFLY-9838 JAVASERVERFACES_SPEC_PUBLIC-671 The old model value is redisplayed on @NotNull validation error with INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true
- Resolved
- is cloned by
-
JBEAP-10241 [GSS](7.0.z) JAVASERVERFACES_SPEC_PUBLIC-671 The old model value is redisplayed on @NotNull validation error with INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true
- Closed
-
JBEAP-15727 [GSS](7.1.z) JAVASERVERFACES_SPEC_PUBLIC-671 The old model value is redisplayed on @NotNull validation error with INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true
- Closed
-
WFLY-11004 The old model value is redisplayed on @NotNull validation error with INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL=true
- Closed
- is incorporated by
-
JBEAP-14236 [GSS](7.1.z) Upgrade jboss-jsf-api_spec from 2.2.13.redhat-1 to 2.2.13.SP2
- Closed