From 9d685b6c1710169ccf79686664f01fd7a80b2af8 Mon Sep 17 00:00:00 2001
From: Christian Bauer <christian@hibernate.org>
Date: Fri, 17 Sep 2004 20:20:48 +0000
Subject: [PATCH] Not best practice removed

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@4564 1b8cb986-b30d-0410-93ca-fae66ebed9b2
---
 reference/en/modules/best_practices.xml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/reference/en/modules/best_practices.xml b/reference/en/modules/best_practices.xml
index 935943fb27..a9400b5669 100644
--- a/reference/en/modules/best_practices.xml
+++ b/reference/en/modules/best_practices.xml
@@ -138,8 +138,7 @@
                     the <literal>Transaction</literal> and close the <literal>Session</literal>. If you don't, Hibernate
                     can't guarantee that in-memory state accurately represents persistent state. As a special case of this,
                     do not use <literal>Session.load()</literal> to determine if an instance with the given identifier 
-                    exists on the database; use <literal>find()</literal> instead. Some exceptions are recoverable, for
-                    example the <literal>StaleObjectStateException</literal> and <literal>ObjectNotFoundException</literal>.
+                    exists on the database; use <literal>find()</literal> instead.
                 </para>
             </listitem>
         </varlistentry>