I do not know exactly what happens, but if I run the debugger I can see thet the page seen by the formcomponents' propertymodels is in a different state than the one actually holding the form components.
I wonder if ajax has something to do with this, because only part of the page is refreshed via ajax. Maybe the parent page and the refreshed ajax panel remain in different serialization graphs? ** Martin 2009/7/28 Vladimir K <[email protected]>: > > trying to undertand what is happening in your case. When the page is > serialized the steam contains the whole graph, including the ListView and > it's items and the page default model and the ListView items models. When > the page is deserialized, the whole graph is restored including page, its > model, items and their models. My understanding is that in your case the > items models are the old ones that was in the previous version of the page, > how could it be? Or I didn't get what you were saying. > > > MartinM wrote: >> >> Or session store.. anyways, that's not relevant. The important fact is >> that the copies are different. >> >> ** >> Martin >> >> 2009/7/28 Martin Makundi <[email protected]>: >>>> why do you get Page instance 2 on page refresh? >>> >>> Wicket always deserializes page state from diskstore.. so it is a copy. >>> >>> ** >>> Martin >>> >>>> >>>> >>>> MartinM wrote: >>>>> >>>>>> please describe the context. I don >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > -- > View this message in context: > http://www.nabble.com/reuseitems-problems-tp24702133p24705851.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]
