Yes all my objects that need to be serialized are being serialized. I put together a workaround. In the onClick() that closes the Modal Window. I called AbstractAjaxTimerBehavior#stop() then waited for a period longer than the Duration of the AbstractAjaxTimerBehavior and then closed the Modal Window. This worked, but it is kinda clunky and I could see cases where it wouldn't. I think what is happening is that the AbstractAjaxTimerBehavior requests are conflicting with the closeing of the Modal Window. I was looking for a way that would close the Modal Window only after the last request/response was made from the AbstractAjaxTimerBehavior.
Is there a way of finding out when the last AbstractAjaxTimerBehavior response comes back from the server before closeing the Modal Window or am I going down the wrong path here? Warren -----Original Message----- From: Mathias Nilsson [mailto:[email protected]] Sent: Thursday, August 27, 2009 12:18 PM To: [email protected] Subject: Re: AbstractAjaxTimerBehavior on Modal Window causes PageExpiredException Does all your models and objects that you use in the wicket page implement Serializable? -- View this message in context: http://www.nabble.com/AbstractAjaxTimerBehavior-on-Modal-Window-causes-P ageExpiredException-tp25159539p25178263.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
