On Jan 7, 2008 1:57 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > No it serializes the page and the object in one file... so the references > keep connected. > Martijn Actually, not quite.
When pageB has reference to pageA and pageB is being serialized, it serializes pageB and pageA separately. So when later pageA is loaded, it's loaded in exact state as it was when pageB was deserialized, thus containing the modified object. -Matej > > > On Jan 7, 2008 1:54 AM, Edvin Syse <[EMAIL PROTECTED]> wrote: > > > > That's too bad, as it works as it's supposed for me now. I would > > > really need to see some code. > > > Do you pass object reference from pageA to pageB, or the entire pageA? > > > > > > because if you have situation like this: > > > > > > pageA holds reference to objectX > > > pageA passes reference to objectX to pageB > > > pageB modifies objectX and returns to pageA > > > > > > it will not work. > > > > > > but if you pass the pageA reference to pageB, so that pageB holds > > > reference to pageA as well as objectX, it should work. > > > > I didn't pass in pageA to PageB and PageC because I didn't need the > > reference to Page A, but if I understand correctly, that will keep the > > page from being serialized or something? It seems to be working now that I > > added pageA to the other two pages, I'll deploy and test a bit > > more, but it seems to be finally working!! :) > > > > -- Edvin > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
