[jira] [Resolved] (WICKET-6856) WicketTester fails do startComponentInPage() after session invalidation

["Sven Meier (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sven Meier resolved WICKET-6856.
--------------------------------
    Resolution: Not A Problem

Testcases are now in-line with what happens in a real web application:
Session#invalidate() prevents access to pages after the request, e.g. in a redirect to render.

> WicketTester fails do startComponentInPage() after session invalidation
> -----------------------------------------------------------------------
>
>                 Key: WICKET-6856
>                 URL: https://issues.apache.org/jira/browse/WICKET-6856
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 8.11.0
>            Reporter: Ilia Naryzhny
>            Assignee: Sven Meier
>            Priority: Minor
>
> Probably issue WICKET-6848 introduced the following issue. If there is a code which does session invalidation first and then starts testing of a component: the last one will fail with something like org.apache.wicket.protocol.http.PageExpiredException: Page with id '0' has expired.
> Simple example:
> {code:java}
> tester.getSession().invalidate();
> tester.startComponentInPage(new AnyPanel("panel"));
> {code}
> But, at the same time starting pages (by class or instance) do not have this negative side effect.
> P.S. Doing `invalidateNow()` will help to solve this particular case, but in our case exactly invalidate() invoked as part of signout - so not a part of actual test case code.
> P.P.S Wicket 8.10.0 didn't have this problem,



--
This message was sent by Atlassian Jira
(v8.3.4#803005)