Wicket Version: 1.3 OK, I'll admit to having a tenuous grasp of Wicket -- but I am trying to learn. I am having trouble with a pages having a very short half life! I have looked at several prior postings on the topic of page expiry but none seem fit the bill.
I have boiled my application down to two very simple pages: Page1.html that has a link to Page2. <a href="#" wicket:id="link_to_page_two">Page Two</a> That's it! Here are the sequence of steps: I invoke the app, Page1 is displayed I click on the link on Page1, Wicket correctly leads me to Page2 I use the browser's back button (I can hear you say aha!) -- Page1 is displayed I click on the link (to Page2) -- I get the "Page Expired" page I can see that this has something to do with the version of the page that is being referenced but beyond that I don't have a rational explanation for what I am seeing. Can you please explain -- or point me to the appropriate docs? Also, what I have described above is a fairly common usage scenario. How can I prevent the user from seeing the "Page expired" page? FWIW, the link to Page2 has been coded as a PageLink. For good measure, I have even tried both PageLink constructor variants. I see the same behavior in both cases. I appreciate any guidance you can provide. Sri -- View this message in context: http://www.nabble.com/Why-has-my-page-expired--tp15283551p15283551.html Sent from the Wicket - User mailing list archive at Nabble.com.
