Message:
The following issue has been closed.
Resolver: Max Rydahl Andersen
Date: Sat, 27 Sep 2003 3:42 PM
We can't encourage building systems that randomly goes of an reopens, reconnect, reaccess the database when you have just explicitly closed the access. It's just not a good idea!
Furthermore it won't ever work for collection wrappers, only for proxies.
You should/could instead reassociate the objects/proxies with a new session by using saveOrUpdate() or even better lock(o, LockMode.NONE); which will reattach the object without performing any save or updates.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-368
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-368
Summary: Allow proxies to load in session other than one that created them
Type: Improvement
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Chris Nokleberg
Created: Sat, 27 Sep 2003 3:20 PM
Updated: Sat, 27 Sep 2003 3:42 PM
Description:
For discussion, please see the following forum topic:
http://forum.hibernate.org/viewtopic.php?t=42
In summary, there are scenarios in which it one may want proxies to be resolved in a different session.
The attached patch adds a ThreadLocal to SessionFactoryImpl which keeps track of the last opened session. If a the session that created a proxy is closed when it comes time to initialize the proxy, the last opened session is used instead, unless it has been closed as well.
---------------------------------------------------------------------
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
|
