the problem is that if you have 2 page that share the same object instance and 1 of the pages get serialized and then deserialized The object instance is not the same anymore
For example this still works: Object A instance PageA has that instance. PageA creates PageB and passes that instance (and itself) PageB is rendered Action executed on PageB PageB sets an internal variable on Object A and then sets PageA as te response page. This only works if the session is not replicated and the Action on B is executed on a different machine. But if somebody goes from PageB to PageC and then uses the back button to get to B and then executes the action The shared instance is not shared anymore (just as session replication) So the best thing is that you shouldnt depend on shared variablen. On Thu, Mar 13, 2008 at 10:42 AM, Maurice Marrink <[EMAIL PROTECTED]> wrote: > Why shouldn't pages share objects? > pushing object x from page a to page b to modify x and then return to > either the same or another instance of page a is just fine. > You can also wrap object x in a model and use that same model on > different pages / components. > > Maurice > > On Thu, Mar 13, 2008 at 10:14 AM, Frank van Lankvelt > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > please excuse my newbie question; is it correct that pages cannot share > > objects? (any pointers on the subject of wickets serialization would > be > > greatly appreciated) > > > > I want to provide some feedback to the main page from a modal-window, > > and now do this by putting meta-data in the session. Is there a > cleaner > > way to do this? > > > > thanks, Frank > > > > --------------------------------------------------------------------- > > 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] > >
