You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ilia Naryzhny (Jira)" <ji...@apache.org> on 2020/11/28 03:05:00 UTC
[jira] [Created] (WICKET-6856) WicketTester fails do
startComponentInPage() after session invalidation
Ilia Naryzhny created WICKET-6856:
-------------------------------------
Summary: 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
Probably issue WICKET-6848 introduce the following issue. If there is a code which do session invalidation first and then start testing of a component: last one will fail.
Simple example:
{code:java}
tester.getSession().invalidate();
tester.startComponentInPage(new AnyMyPanel("panel"));
{code}
But, at the same time starting of 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 out case exactly invalidate() invoked as part of signout - so not a part of actual testcase code.
P.P.S Wicket 8.10.0 didn't have this problem,
--
This message was sent by Atlassian Jira
(v8.3.4#803005)