Mike, in reference to your various questions, here is my take: You are not seeing your constructor tracing print statements because it is not invoked more than once (the page object is already in the page store, with its component attached as per the constructor invocation) - all components are the same, but the data can vary depending on your model as observed. This is the case for stateful, or non-bookmarkable pages.
Bookmarkable pages are re-instantiated and must be given their state if any, at construction time. That is how Wicket decides whether to go back to the page store or use a new instance. I believe Bookmarkable links are there to accomodate fast access to stateless pages or stateful pages with the state encoded in the request. On Fri, Sep 10, 2010 at 8:36 PM, Mike Dee <mdichiapp...@cardeatech.com>wrote: > > But why? > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Demystifying-page-serialization-tp2533538p2535266.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
