openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r936440 - in /openjpa/branches/2.0.x: ./ openjpa-project/src/doc/manual/ref_guide_runtime.xml
Date Wed, 21 Apr 2010 18:54:35 GMT
Author: curtisr7
Date: Wed Apr 21 18:54:35 2010
New Revision: 936440

OPENJPA-1604: Doc update.

    openjpa/branches/2.0.x/   (props changed)

Propchange: openjpa/branches/2.0.x/
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Apr 21 18:54:35 2010
@@ -1,2 +1,2 @@

Modified: openjpa/branches/2.0.x/openjpa-project/src/doc/manual/ref_guide_runtime.xml
--- openjpa/branches/2.0.x/openjpa-project/src/doc/manual/ref_guide_runtime.xml (original)
+++ openjpa/branches/2.0.x/openjpa-project/src/doc/manual/ref_guide_runtime.xml Wed Apr 21
18:54:35 2010
@@ -936,6 +936,24 @@ state in question to circumvent the data
 from issuing a locking SELECT in the first place.
+                <listitem>
+                    <para>
+When using the pessimistic lock manager and named queries you will see the following
+<literal>WARNING</literal> message logged if you do not specify a lockMode on
the named query
+or you explicitly set it to <literal>LockModeType.NONE</literal>. When using
the pessimistic
+lock manager a <literal>LockModeType.NONE</literal> will always be promoted to
+WARN   [main] openjpa.MetaData - Encountered a read lock level less than LockModeType.READ
when processing the NamedQuery annotation "findEmployeeById" in class "org.apache.openjpa.persistence.lockmgr.LockEmployee".
Setting query lock level to LockModeType.READ.
+If you are using the pessimistic lock manager and you truly do want to set the lock mode
to NONE for a
+given query, you can use a fetch plan to do so.
+OpenJPAQuery q = em.createNamedQuery("findEmployeeById"); 
+FetchPlan fp = q.getFetchPlan();
+                    </para>
+                </listitem>                

View raw message