[CHAIN-30] ServletSessionScopeMap always forces a Session to be Created

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.1
• Assignee: Niall Pemberton
• Reporter: Niall Pemberton
• Created: 08/Jun/06 09:19
• Updated: 02/Jan/08 07:01
• Resolved: 08/Jun/06 23:42

Description

The current implementation of ServletSessionScopeMap always forces a Session to be created whenever getSessionScope() is called on ServletWebContext.

This could be avoided and would be smarter if ServletSessionScopeMap was instantiated with the HttpServletRequest rather than the HttpSession - that way if no Session exists it could be lazily created only during write operations on the Map.

Frameworks such as Struts check session scope for various attributes for each request processed - if it used this abstracted Map representaion of session scope it would mean a session is always created (if it doesn't already exist) whether its needed or not.