From: Steve E. (JIRA) <no...@at...> - 2006-07-16 12:30:59
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1584?page=all ] Steve Ebersole closed HHH-1584: ------------------------------- Resolution: Duplicate HHH-1818 > Trying to get a deleted object --> ObjectDeletedException > --------------------------------------------------------- > > Key: HHH-1584 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1584 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.3 > Environment: Linux, Oracle, Tomcat > Reporter: Nicolas Ternisien > > > As explained here : > http://forum.hibernate.org/viewtopic.php?t=940989&highlight=objectdeletedexception > When you try to get an entity in the same Session / Transaction, after delete it, the ObjectDeletedException is thrown. > It will be easier if the get() method from Session interface only returns a null instance, instead of launching an exception. > This case forces developers to flush the current session, to remove the deleted instance from it. > So I think it can reduce speed of an application. > JUnit test, stack trace and some other explanations are available in the forum page. > Cheers. -- 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 |