Thanks Martijn, Yes it is the homepage. If I set it up as you mentioned, I have some doubts as to what happens under the hood. I access the homepage first, page instance is in session. When I click the link to increment the counter, no new page is created, but wicket keeps a copy of the page in its original (zero counter) state on the disk, and the current one (incremented) in session?
On Jan 9, 2008 12:30 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > The page is probably your homepage and the homepage is referenced using a > bookmarkable link. The bookmarkable URL is causing the reconstruction of > the > page. > If you mount the page using a Hybrid url encoding strategy, it will work > as > you expect. > > Martijn > > On 1/9/08, Don Parsons <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > I'm new here. I'm just starting to learn wicket. And only done simple > JSPs > > before. I'm trying a very simple example, and I just want to understand > > how > > things are working in wicket. I've made just one page, where it has a > > counter link, when I click the link I increment the counter, which a > Label > > in the page has its PropertyModel based on (the counter). It all works > > fine, > > but I noticed that, when I click the back button of the browser, the > > constuctor on my page is called again, and I'm back at zero. My > > understanding is that the previous page is stored on disk, so shouldnt > > clicking the back button show you the page with its old state (zero > > counter) > > but without creating a page instance again? > > > > Thanks. > > > > > > -- > 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 >
