[ http://issues.apache.org/jira/browse/CHAIN-30?page=all ]
Niall Pemberton resolved CHAIN-30:
----------------------------------
Fix Version: 1.1
Resolution: Fixed
Assign To: Niall Pemberton
> ServletSessionScopeMap always forces a Session to be Created
> ------------------------------------------------------------
>
> Key: CHAIN-30
> URL: http://issues.apache.org/jira/browse/CHAIN-30
> Project: Commons Chain
> Type: Bug
> Versions: 1.0 Release
> Reporter: Niall Pemberton
> Assignee: Niall Pemberton
> Fix For: 1.1
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
