[
https://issues.apache.org/jira/browse/WICKET-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-3487.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.17
Assignee: Igor Vaynberg
> RequestCycle.steps() creates a session on abort even if none exists
> -------------------------------------------------------------------
>
> Key: WICKET-3487
> URL: https://issues.apache.org/jira/browse/WICKET-3487
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.4.14
> Reporter: Tom Palmer
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.17
>
>
> During abort exception handling, RequestCycle.steps() calls getSession() to
> check if the session is invalidated (part of the solution to WICKET-2013).
> Unfortunately, this has the side-effect of creating a new session if none
> exists. Ideally, this should first call Session.exists() to see if a session
> is even bound to the current thread. If not, no action needs to be taken to
> still meet the needs of 2013.
> The ultimate goal is to be able to abort an initial request (e.g. via
> exception thrown from RequestCycle.onBeginRequest()) without incurring the
> overhead of a useless session.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
