I am really sorry, after detail tracing system, I found that there is
some parts of code will throw
RestartResponseAtInterceptPageException...
On 12/27/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
set a breakpoint in your auth strategy and see what it is doing, sounds like
a bug in there
-igor
Anyone have any idea?
On 12/22/06, Carfield Yim [EMAIL PROTECTED] wrote:
The unit test is just create a WebPage and assert it, stacktrace as
below and look like the authenication will forward to Logon page if it
is not authenication . However, in the session I have set it always
return true
well looks like you are expecting main page but getting a login? so your
auth strategy is redirecting, thus the test fails
-igor
On 12/26/06, Carfield Yim [EMAIL PROTECTED] wrote:
Anyone have any idea?
On 12/22/06, Carfield Yim [EMAIL PROTECTED] wrote:
The unit test is just create a
On 12/27/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
well looks like you are expecting main page but getting a login? so your
auth strategy is redirecting, thus the test fails
But for the unit test session, I already did below:
public static class Tester extends WicketTester {
set a breakpoint in your auth strategy and see what it is doing, sounds like
a bug in there
-igor
On 12/26/06, Carfield Yim [EMAIL PROTECTED] wrote:
On 12/27/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
well looks like you are expecting main page but getting a login? so your
auth strategy is
The unit test is just create a WebPage and assert it, stacktrace as
below and look like the authenication will forward to Logon page if it
is not authenication . However, in the session I have set it always
return true if it is unit test. Anybody have any idea?
junit.framework.ComparisonFailure:
