[
https://issues.apache.org/jira/browse/WICKET-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-574.
----------------------------------
Assignee: Juergen Donnerstag
Fix Version/s: 1.5-M1
(was: 1.5-M2)
Resolution: Fixed
looks like juergen fixed this in 1.5
> WicketTester does not bind created Session to SessionStore
> ----------------------------------------------------------
>
> Key: WICKET-574
> URL: https://issues.apache.org/jira/browse/WICKET-574
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta1
> Reporter: Gerry Lowe
> Assignee: Juergen Donnerstag
> Priority: Minor
> Fix For: 1.5-M1
>
>
> The WicketTester constructor, via a call to
> MockWebApplication.createRequestCycle(), creates a new session but fails to
> bind it:
> this.wicketSession = (WebSession) Session.findOrCreate();
> This means that the session subsequently gets over-written by a new one
> created in a later call to WicketTester.startPage(). This causes problems
> for any unit tests which want to set up session data after instantiating a
> WicketTester, but before calling WicketTester.startPage().
> The MockWebApplication.createRequestCycle() should probably bind the session
> immediately after creating it:
> this.wicketSession = (WebSession) Session.findOrCreate();
> getApplication().getSessionStore().bind(getWicketRequest(),
> wicketSession);
> Then subsequent calls to startPage() will use this session rather than create
> a new one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
