Show us the stacktrace.
On Fri, Apr 19, 2013 at 4:36 PM, Nick Pratt nbpr...@gmail.com wrote:
Has anything changed in the Wicket 6.x branch with regards to page
instantiation and authentication?
I had code that was working that did the following:
Page page = new MyAuthProtectedPage(
There is no stack. All I see in the Exception is:
org.apache.wicket.RestartResponseAtInterceptPageException
Nick
On Fri, Apr 19, 2013 at 9:42 AM, Martin Grigorov mgrigo...@apache.orgwrote:
Show us the stacktrace.
On Fri, Apr 19, 2013 at 4:36 PM, Nick Pratt nbpr...@gmail.com wrote:
Sounds like you have modified your authorization to instantiation, and when
the person trying to access the page was not yet logged in, you get during
construction an exception that you can't construct the page (causing the
redirect).
Martijn
On Fri, Apr 19, 2013 at 4:17 PM, Nick Pratt
Correct.
RestartResponseAtInterceptPageException is optimized to not load the stack
trace because it is used for flow control.
Now the question is where the exception is being catched and logged ?
Additionally what you are doing is fishy.
You keep an instance of a page in another page and you use
