You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Thomas Andraschko (JIRA)" <de...@myfaces.apache.org> on 2018/01/16 20:19:00 UTC
[jira] [Commented] (MYFACES-3181) wrong behaviour in combination
with javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL
[ https://issues.apache.org/jira/browse/MYFACES-3181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327722#comment-16327722 ]
Thomas Andraschko commented on MYFACES-3181:
--------------------------------------------
[~wtlucy] [~eduardobreijo] I think this should be fixed the other ticket last week? Lets close it?!
> wrong behaviour in combination with javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL
> -----------------------------------------------------------------------------------------------
>
> Key: MYFACES-3181
> URL: https://issues.apache.org/jira/browse/MYFACES-3181
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.6
> Reporter: Gerhard Petracek
> Assignee: Leonardo Uribe
> Priority: Major
>
> constellation:
> javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL
> + a property annotated with @NotNull
> if an input component has a value and it gets removed by the user, a validation error occurs as expected but the old value of the model gets displayed instead of the wrong value (which is the empty string)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)