Martin,
please describe the context. I don't see how the process of serialization
makes the instance of the object obsolete.
In my practice I use a detachable model when rendering View page and I use a
static model when rendering an Edit page. In onSubmit method I save the
model object and
please describe the context. I don't see how the process of serialization
makes the instance of the object obsolete.
1. Page instantiation. Page instance 1 {manipulating target data 1},
formComponent instance 1-target data instance 1.
2. Ajax request or similar onto page.
3. Page refresh
Martin,
why do you get Page instance 2 on page refresh?
MartinM wrote:
please describe the context. I don't see how the process of serialization
makes the instance of the object obsolete.
1. Page instantiation. Page instance 1 {manipulating target data 1},
formComponent instance
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:
Or session store.. anyways, that's not relevant. The important fact is
that the copies are different.
**
Martin
2009/7/28 Martin Makundi martin.maku...@koodaripalvelut.com:
why do you get Page instance 2 on page refresh?
Wicket always deserializes page state from diskstore.. so it is a copy.
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,
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
Hmm ... i can imagine the only case - somewhere resolveObject() method is
called during deserialization.
But I'm afraid your code don't have such a method and the cause is
different.
MartinM wrote:
I do not know exactly what happens, but if I run the debugger I can
see thet the page seen by
It might also be that it is wickettester related problem, maybe
something goes somehow wrong there. I will try to make a quickstart.
**
Martin
2009/7/29 Vladimir K koval...@gmail.com:
Hmm ... i can imagine the only case - somewhere resolveObject() method is
called during deserialization.
But
