Re: Page references and serialization

2008-11-17 Thread Johan Compagner
references and serialization Doesnt have to be a bug, (it could be a new version of page a) but besides that dont we have a sliding window in the pagemap, so if page a is touched shouldnt it get its own new place in the file (more 2 the top) so that it doesnt get overwritten later on to early

RE: Page references and serialization

2008-11-16 Thread Mikko Pukki
, Mikko Pukki -Original Message- From: Johan Compagner [mailto:[EMAIL PROTECTED] Sent: 14. marraskuuta 2008 21:10 To: users@wicket.apache.org Subject: Re: Page references and serialization Doesnt have to be a bug, (it could be a new version of page a) but besides that dont we have a sliding

Re: Page references and serialization

2008-11-14 Thread Martijn Dashorst
iirc Wicket serialization is smart enough to discover that PageA should not be serialized as part of PageB, but instead will replace it with a reference to PageA's serialized instance. Martijn On Fri, Nov 14, 2008 at 7:15 AM, Igor Vaynberg [EMAIL PROTECTED] wrote: if you are using 1.4rc1 there

Re: Page references and serialization

2008-11-14 Thread Matej Knopp
That would be a bug then. What wicket version are you using? -Matej On Fri, Nov 14, 2008 at 4:11 PM, Cristiano Kliemann [EMAIL PROTECTED] wrote: Martijn, I'm pretty sure it is serializing PageA again. I've put some breakpoints to confirm it (at DiskPageStore.PageSavingThread.run()). Also,

Re: Page references and serialization

2008-11-14 Thread Cristiano Kliemann
Tested with 1.3.2, 1.3.3, 1.3.4, 1.3.5 and 1.4-rc1 with the exact same results. With 1.3.0 and 1.3.1, it goes to 89KB instead of 64KB. Is it really an unexpected behavior? If a PageB holds a reference to PageA, it can change PageA state. The serialized version has an old, invalid state then. When

Re: Page references and serialization

2008-11-14 Thread Johan Compagner
Doesnt have to be a bug, (it could be a new version of page a) but besides that dont we have a sliding window in the pagemap, so if page a is touched shouldnt it get its own new place in the file (more 2 the top) so that it doesnt get overwritten later on to early? On 11/14/08, Matej Knopp

Page references and serialization

2008-11-13 Thread Cristiano Kliemann
Hi! Some questions about Wicket serialization... Let's say I have two pages, A and B, and page B holds a reference to page A. First, an instance of page A is rendered and gets serialized by Wicket. Then the user clicks on a button that creates an instance of page B, sets a reference to the

Re: Page references and serialization

2008-11-13 Thread James Carman
Do the pages you need to go back to need to be the exact same instances (do you need that exact state)? On Thu, Nov 13, 2008 at 9:20 PM, Cristiano Kliemann [EMAIL PROTECTED] wrote: Hi! Some questions about Wicket serialization... Let's say I have two pages, A and B, and page B holds a