From: <leg...@at...> - 2003-09-27 21:04:20
|
The following comment has been added to this issue: Author: Gavin King Created: Sat, 27 Sep 2003 4:03 PM Body: Chris, Max and I are discussing this (in Aarhus). I think we would accept something like this if: (1) it worked by calling Session.lock() (2) it worked for collections (which would require that a collection wrapper keep a pointer back to the owning entity, so that it could lock() the owner) (3) we could turn this feature off --------------------------------------------------------------------- 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 |