Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-6856

WicketTester fails do startComponentInPage() after session invalidation

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Not A Problem
    • Affects Version/s: 8.11.0
    • Fix Version/s: None
    • Component/s: wicket-core
    • Labels:
      None

      Description

      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:

      tester.getSession().invalidate();
      tester.startComponentInPage(new AnyPanel("panel"));
      

      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,

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              svenmeier Sven Meier
              Reporter:
              phantom Ilia Naryzhny

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment