[WICKET-5040] Session.exists() returns false when ThreadContext#session is not set to current session

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.5.0
• Fix Version/s: 6.6.0
• Component/s: wicket
• Assignee: Sven Meier
• Reporter: Sven Meier
• Created: 14/Feb/13 10:41
• Updated: 14/Feb/13 14:44
• Resolved: 14/Feb/13 14:44

Description

There are several places in Wicket which check for the existence of a Session before actually getting a reference to it, e.g. FeedbackCollector:

public final List<FeedbackMessage> collect(final IFeedbackMessageFilter filter)
{
...
if (includeSession && Session.exists())

{ messages.addAll(Session.get().getFeedbackMessages().messages(filter)); }

}

If no one has called Session#get(), all calls to Session#exists() return false although a session might exist in the session store, i.e. it might just not be set to ThreadContext#session already.

Issue Links

• breaks: WICKET-5036 Post Parameters are lost when continueToOriginalDestination() is called