[hibernate-commits] Hibernate SVN: r11205 - branches/Branch_3_2/HibernateExt/annotations/doc/reference/en/modules.

[hibernate-commits at lists.jboss.org]

Author: epbernard
Date: 2007-02-13 21:47:15 -0500 (Tue, 13 Feb 2007)
New Revision: 11205

Modified:
   branches/Branch_3_2/HibernateExt/annotations/doc/reference/en/modules/entity.xml
Log:
EJBTHREE-774

Modified: branches/Branch_3_2/HibernateExt/annotations/doc/reference/en/modules/entity.xml
===================================================================
--- branches/Branch_3_2/HibernateExt/annotations/doc/reference/en/modules/entity.xml	2007-02-14 02:39:17 UTC (rev 11204)
+++ branches/Branch_3_2/HibernateExt/annotations/doc/reference/en/modules/entity.xml	2007-02-14 02:47:15 UTC (rev 11205)
@@ -33,7 +33,7 @@
     tests have been designed to represent a concrete example and be a
     inspiration source.</para>
 
-    <sect2>
+    <sect2 id="entity-mapping-entity">
       <title>Declaring an entity bean</title>
 
       <para>Every bound persistent POJO class is an entity bean and is
@@ -108,7 +108,7 @@
         about that.</remark>
       </sect3>
 
-      <sect3>
+      <sect3 id="entity-mapping-entity-version" revision="1">
         <title>Versioning for optimistic locking</title>
 
         <para>You can add optimistic locking capability to an entity bean
@@ -132,6 +132,11 @@
         or a timestamp as per the EJB3 spec. Hibernate support any kind of
         type provided that you define and implement the appropriate
         <classname>UserVersionType</classname>.</para>
+
+        <para>The application must not alter the version number set up
+        by Hibernate in any way. To artificially increase the version number,
+        check in Hibernate Entity Manager's reference documentation
+        <literal>LockMode.WRITE</literal></para>
       </sect3>
     </sect2>