Hi, Only the last used instance of the page is stored in the session. And only if this page is stateful. Wicket does this because if the page is stateful and you have a Link in that page for example then clicking on this Link will execute its #onClick() method. To be able to execute it Wicket finds the stored page instance, finds the Link in the page's component tree and executes the method. Without this, Wicket will create a new instance of the page, find the Link and execute its method - this is how stateless page work. Pages are stateless by default until you add the first stateful component or behavior to it.
If you go several pages back (you press several times the back button) then Wicket will read the page from the disk store. Read https://cwiki.apache.org/confluence/x/qIaoAQ for more details. On Tue, Apr 24, 2012 at 3:34 PM, Philipp Oppermann <p.opperm...@googlemail.com> wrote: > Hi, I'm PHP-Programmer and now switching to java (and wicket ;) ). But > one thing confuses me: > > Why everything is stored in Session? > > In PHP the session is empty except you put something in. And there's > no "Back-button-problem" in PHP, when you go back then the site with > the previous URL will be loaded. > > So why you need to store so much in the session? > > Philipp Oppermann > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
