From: Mike H. (JIRA) <no...@at...> - 2005-09-22 21:47:02
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HB-368?page=comments#action_19913 ] Mike Hogan commented on HB-368: ------------------------------- Why was this issue rejected? The thread seemed to be going well towards agreement to find an approach, then nothing except "Status: Rejected". I am looking for a feature like this. Maybe implemented by way of a SessionReattachmentPolicy that allows the Hibernate user have some say about what happens when AbstractLazyInitializer does this: else if ( !session.isOpen() ) { throw new LazyInitializationException("could not initialize proxy - the owning Session was closed"); } Can somebody please explain what happened to this issue? Thanks very much. Mike > Allow proxies to load in session other than one that created them > ----------------------------------------------------------------- > > Key: HB-368 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-368 > Project: Hibernate2 > Type: Improvement > Components: core > Versions: 2.1 > Reporter: Chris Nokleberg > Attachments: lazypatch.txt > > > 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. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira |