[
https://issues.apache.org/jira/browse/WICKET-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pedro Santos resolved WICKET-3809.
----------------------------------
Resolution: Not A Problem
Assignee: Pedro Santos
Hi Andera, I tested the quick start and don't see a problem. ModalWindow adds
an behavior as the close callback in the main page tree, after this page gets
serialized with the "initial value" set in MyBean. When an request hits this
callback, it is natural to expect to find "initial value" when accessing the
serialized model, this is the price of using static models. You can change your
app to use a dynamic model instead.
> ModalWindow with Page as content doesn't change parent Page's version
> ----------------------------------------------------------------------
>
> Key: WICKET-3809
> URL: https://issues.apache.org/jira/browse/WICKET-3809
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.4.17, 1.5-RC4
> Reporter: Andera Del Bene
> Assignee: Pedro Santos
> Attachments: quickStart.zip
>
>
> Let's have a ModalWindow with a page as content (not a panel). In this
> window we access to parent page's model and we perform some changes on it.
> When we close ModalWindow wicket restore the original version of parent page,
> without model's changes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
