|
From: <leg...@at...> - 2003-08-09 14:09:14
|
Message:
The following issue has been closed.
Resolver: Gavin King
Date: Sat, 9 Aug 2003 9:08 AM
A session should never, ever be re-used by a new user. Its lifetime should be much shorter than a HttpSession. I can't think of a good usecase for this and it is anyway possible to manipulate the Interceptor by keeping a reference to it.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-54
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-54
Summary: Flexible Interceptor Assignment
Type: New Feature
Status: Closed
Priority: Minor
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.0rc2
2.1
Assignee: Gavin King
Reporter: Christian Bauer
Created: Mon, 5 May 2003 9:19 AM
Updated: Sat, 9 Aug 2003 9:08 AM
Description:
Interceptors are currently only assignable via SessionFactory configuration or Session creation (constructor parameter). This is not flexible enough for an application with Session Disconnection, e.g. while using the AuditInfo Interceptor Pattern:
- a Session is created with a new interceptor, the current user is passed as a parameter to the interceptor
- the Session will be disconnected/reconnected multiple times
- the user's id may change (logout/login/relogin/...), there's no way to pass a new interceptor to an existing Session or to modify/recall the existing interceptor
An Interceptor should be handled more dynamically, like with getInterceptor()/setInterceptor() methods of the Session. Is this possible or is the Interceptor required at Session instantiation?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|