You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Benjamin Ernst <be...@gmail.com> on 2007/10/09 13:50:03 UTC
ModalWindow serialization problem
Hi guys,
we have a problem with some ModalWindows. We are using a lot of them in our
application and they are often nested in other ModalWindows.
The problem is when we refer to the to the parent that creates the
ModalWindow in this ModalWindow that parent-object is not same as the
parent-object the WindowClosedCallback is in.
This only happen if there are more than 3 nested ModalWindows. Could be a
problem with serialization: The parent-object gets serialized and on the
WindowClosedCallback it gets deserialized. But the changes made in between
this time are now lost.
If that is right? How can we prevent the parent from being serialized?
-Benjamin
Re: ModalWindow serialization problem
Posted by MarcNuri <ma...@marcnuri.com>.
Hi.
Although this thread is quite old, I'm facing the same problem.
I open a modal window to edit a record. Inside this modalwindow I open
another to choose an object. Inside this third one I open another to filter
the objects to choose by another object.
If the last modalwindow isn't opened, everything works fine.
If I open the fourth modalwindow, the closedcallback of the third refers to
data set before the fourth modalwindow was open.
It's a very strange problem, hope that someone can help. Thanks!
Benjamin Ernst wrote:
>
> Sorry, I am quite busy right now. But I will find some time in the next
> days
> and than provide a quickstart.
> In the mean time we fixed the problem by saving the needed Objects in the
> Session-MetaData. And that seems to work.
>
> Thanks for your help!
>
> -Benjamin
>
>
> 2007/10/9, Matej Knopp <ma...@gmail.com>:
>>
>> More then 3 nested ModalWindows? Wow.
>> Does this happen with the latest trunk? Also each modal window is
>> supposed to by in own pagemap. Can you provide a quickstart?
>>
>> -Matej
>>
>> On 10/9/07, Benjamin Ernst <be...@gmail.com> wrote:
>> > Hi guys,
>> >
>> > we have a problem with some ModalWindows. We are using a lot of them in
>> our
>> > application and they are often nested in other ModalWindows.
>> > The problem is when we refer to the to the parent that creates the
>> > ModalWindow in this ModalWindow that parent-object is not same as the
>> > parent-object the WindowClosedCallback is in.
>> >
>> > This only happen if there are more than 3 nested ModalWindows. Could be
>> a
>> > problem with serialization: The parent-object gets serialized and on
>> the
>> > WindowClosedCallback it gets deserialized. But the changes made in
>> between
>> > this time are now lost.
>> >
>> > If that is right? How can we prevent the parent from being serialized?
>> >
>> > -Benjamin
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
--
View this message in context: http://old.nabble.com/ModalWindow-serialization-problem-tp13114045p26674701.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: ModalWindow serialization problem
Posted by Benjamin Ernst <be...@gmail.com>.
Sorry, I am quite busy right now. But I will find some time in the next days
and than provide a quickstart.
In the mean time we fixed the problem by saving the needed Objects in the
Session-MetaData. And that seems to work.
Thanks for your help!
-Benjamin
2007/10/9, Matej Knopp <ma...@gmail.com>:
>
> More then 3 nested ModalWindows? Wow.
> Does this happen with the latest trunk? Also each modal window is
> supposed to by in own pagemap. Can you provide a quickstart?
>
> -Matej
>
> On 10/9/07, Benjamin Ernst <be...@gmail.com> wrote:
> > Hi guys,
> >
> > we have a problem with some ModalWindows. We are using a lot of them in
> our
> > application and they are often nested in other ModalWindows.
> > The problem is when we refer to the to the parent that creates the
> > ModalWindow in this ModalWindow that parent-object is not same as the
> > parent-object the WindowClosedCallback is in.
> >
> > This only happen if there are more than 3 nested ModalWindows. Could be
> a
> > problem with serialization: The parent-object gets serialized and on the
> > WindowClosedCallback it gets deserialized. But the changes made in
> between
> > this time are now lost.
> >
> > If that is right? How can we prevent the parent from being serialized?
> >
> > -Benjamin
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: ModalWindow serialization problem
Posted by Matej Knopp <ma...@gmail.com>.
More then 3 nested ModalWindows? Wow.
Does this happen with the latest trunk? Also each modal window is
supposed to by in own pagemap. Can you provide a quickstart?
-Matej
On 10/9/07, Benjamin Ernst <be...@gmail.com> wrote:
> Hi guys,
>
> we have a problem with some ModalWindows. We are using a lot of them in our
> application and they are often nested in other ModalWindows.
> The problem is when we refer to the to the parent that creates the
> ModalWindow in this ModalWindow that parent-object is not same as the
> parent-object the WindowClosedCallback is in.
>
> This only happen if there are more than 3 nested ModalWindows. Could be a
> problem with serialization: The parent-object gets serialized and on the
> WindowClosedCallback it gets deserialized. But the changes made in between
> this time are now lost.
>
> If that is right? How can we prevent the parent from being serialized?
>
> -Benjamin
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org