Hi, It is a bit more complicated.
On Tue, May 29, 2012 at 7:00 PM, sudeivas <sureshkumar....@gmail.com> wrote: > With the above code changes, I made a simple test case, > > 1. Ajax Button which will throw StalePageException. > Result: The page reloaded itself without going to the error page. > > 2. Ajax Button which will throw PageExpiredException. > Result: Error page This is correct. Only MountedMapper can "revive" a page if org.apache.wicket.settings.IPageSettings#setRecreateMountedPagesAfterExpiry() is true. This is because MountedMapper knows the Page's class and is able to create a new instance. If only the page id is available then we do not know which page class to use. > > 3. Ajax Button which will throw ComponentNotFoundException. > Result: Error page See the inline comments in org.apache.wicket.request.handler.ListenerInterfaceRequestHandler#respond for more info about this. > > I believe for all the above use cases, the page should reload instead of > going to the error page. > > Please let me know if I missing something. Advice: Avoid handling Wicket's internals in your code unless really necessary. > > Thanks, > Suresh > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Getting-more-stale-page-exception-in-wicket-1-5-6-tp4649492p4649550.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
