Re: Questions about how wicket serialization works

> Wicket stores > 1. the page, > 2. component hierarchy, > 3. and associated models (the state) in the page store." > > By "only the serialized form of the page hierarchy is stored.", you mean the > first two things? The page == component hierarchy and associated models are part of it because the

Re: Questions about how wicket serialization works

Erik, Thanks so much for reply to my questions. >>No, only the serialized form of the page hierarchy is stored. What do you exactly mean? WiA mentions three things: Wicket stores 1. the page, 2. component hierarchy, 3. and associated models (the state) in the page store." By "only the seria

Re: Questions about how wicket serialization works

Answers below... David Chang wrote: I am reading the book Wicket in Action. Page 88 about serializing models says: "At the end of the request, after the markup has been sent to the browser, Wicket stores the page, component hierarchy, and associated models (the state) in the page store." Do

Questions about how wicket serialization works

I am reading the book Wicket in Action. Page 88 about serializing models says: "At the end of the request, after the markup has been sent to the browser, Wicket stores the page, component hierarchy, and associated models (the state) in the page store." Does "Wicket stores the page" means Wicke