Hi Dirk,
overriding #onUnauthorizedInstantiation() wouldn't help you, since
#restartResponseAtSignInPage() overwrites the old interceptData with a
new one.
You're the one to decide when the interceptData can be cleared: In the
page constructor would be a possibility. An IRequestCycleListener would
be another one.
Sven
On 06/05/2013 07:23 AM, Dirk Forchel wrote:
Any idea? Any hint? Or should I add clearInterceptData() to the constructor
of each Page class with authorized access? A short description in source
code would be helpful.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/WICKET-4500-WICKET-5140-and-RestartResponseAtInterceptPageException-clearOriginalDestination-tp4659205p4659242.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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
