I tried it on IE 7 and Firefox. on IE the constructor is called. On firefox, back gets a cached page, and the constuctor isnt called. Is this as expected?
On Jan 9, 2008 7:59 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > this seems a little odd that the back button itself causes the > constructor to be invoked agian. that would mean that the browser > never actually caches the page at all and on the back button issues > another request to the server. can you confirm that this is indeed > what is happening? > > -igor > > > On Jan 9, 2008 2:17 AM, 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. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
