Martin, Yes our Application.init method is where we register a IAuthorizationStrategy and a IUnauthorizedComponentInstantiationListener. Do those override the setPageExpiredErrorPage() somehow? I'm trying to understand the interplay so that I can give our users a meaningful message when they click something after the session expires.
We have a custom IExceptionMapper as well but that never gets called when I am reproducing this. What does get called is the onUnauthorizedInstantiation method and it redirects to a login page since the user is not logged in. In that method there is no way for me to know if it was an unauthorized instantiation because of a session timeout or because of some other reason. If you need a quickstart I can create one. I just figured this is such a common thing that someone might be able to point me in the right direction. Thanks, Josh -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Understanding-setPageExpiredErrorPage-and-onUnauthorizedInstantiation-tp4663870p4663891.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
