[jira] Resolved: (WICKET-1688) FeedbackMessageModel gets wrong states between requests

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-1688.
-----------------------------------

    Resolution: Invalid
      Assignee: Igor Vaynberg

dont think we should support that debug option...

further, component#tostring() has already been changed not to access the model by default so this should no longer be an issue for you.

> FeedbackMessageModel gets wrong states between requests
> -------------------------------------------------------
>
>                 Key: WICKET-1688
>                 URL: https://issues.apache.org/jira/browse/WICKET-1688
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4-M1
>            Reporter: xiefei
>            Assignee: Igor Vaynberg
>
> In the first request, the FeedbackMessagesModel.messages becomes null when RequestCycle.detach() is called. But during the page serialization phase,  the FeedbackMessagesModel.getObject() is called and FeedbackMessagesModel.messages go back to the state before RequestCycle.detach(),  that is an EmptyList.
> then in the next (ajax) request , FeedbackMessagesModel.messages is always an EmptyList and never has a chance to get messages from Session.
> The call stack in the serialization phase :
> FeedbackMessagesModel.getObject()
> MessageListView.getModelObject()
> FeedbackPanel.getCurrentMessages()
> FeedbackPanel.anyMessage()
> FeedbackPanel.isVisible()
> FeedbackPanel.determinVisibility()
> FeedbackPanel.toString()
> ...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.