[jira] [Commented] (WICKET-6215) Test fail when non empty model is set to PasswordTextField

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391140#comment-15391140 ] 

ASF subversion and git services commented on WICKET-6215:
---------------------------------------------------------

Commit 6ebd64afc878a45b070d72adfcda797b9550fe08 in wicket's branch refs/heads/wicket-7.x from [~svenmeier]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=6ebd64a ]

WICKET-6215 use getModel().setObject(null) ínstead


> Test fail when non empty model is set to PasswordTextField
> ----------------------------------------------------------
>
>                 Key: WICKET-6215
>                 URL: https://issues.apache.org/jira/browse/WICKET-6215
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 8.0.0-M1, 7.5.0
>         Environment: JUnit tests with WicketTester.
>            Reporter: Kevin Leturc
>            Assignee: Sven Meier
>
> Since WICKET-6211 changes, when we set a non empty model to PasswordTextField, junit tests which try to start and assert rendered page failed.
> This is due to the clean of password text field model object, when component is detached, which makes the page dirty, then create a new page id and finally send a redirect. At the end we have an infinite loop in request execution, and test failed on "Possible infinite redirect detected. Bailing out.".
> One possible solution is to change the call setModelObject(null) (responsible of dirty state) by getModel().setObject(null) in PasswordTextField.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)