On Sat, Mar 31, 2012 at 12:29 AM, sudeivas <sureshkumar....@gmail.com> wrote: > Thanks for the information. I am currently using wicket 1.5.3. > > I hope this applies to wicket-1.5.3 as well.
Yes > > But in my case, everything works fine. But when our session management > fails, then we run into the following exceptions: > > PageExpiredException > ComponentNotFoundException > StalePageException This is normal. If there is no page with that version in the store then PageExpiredException is thrown. > > Please let me know if enabling page version will fix any of these issues. > Also in 6.x I see an API called > setRecreateMountedPagesAfterExpiry() > > Is this option available already in wicket-1.5.3 (by default true) ? If not, > what happens when a page expires? It is available since 1.5.4. When page is expired Wicket will create a new instance of this page as its javadoc explains. > > Thanks, > Suresh > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Version-Pages-by-default-tp4520432p4520613.html > Sent from the Users forum 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 > -- 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
