[Hibernate-commits] Hibernate3/test/org/hibernate/test/ejb3/lock EJB3LockTest.java,1.1,1.2

[<ste...@us...>]

Update of /cvsroot/hibernate/Hibernate3/test/org/hibernate/test/ejb3/lock
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19702/test/org/hibernate/test/ejb3/lock

Modified Files:
	EJB3LockTest.java 
Log Message:
read-committed isolation protections

Index: EJB3LockTest.java
===================================================================
RCS file: /cvsroot/hibernate/Hibernate3/test/org/hibernate/test/ejb3/lock/EJB3LockTest.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- EJB3LockTest.java	14 Feb 2006 03:24:18 -0000	1.1
+++ EJB3LockTest.java	17 Feb 2006 03:14:14 -0000	1.2
@@ -36,8 +36,6 @@
 
 	protected void configure(Configuration cfg) {
 		super.configure( cfg );
-//      error on Oracle 10g
-//		cfg.setProperty( Environment.ISOLATION, "" + java.sql.Connection.TRANSACTION_READ_UNCOMMITTED );
 		cfg.setProperty( Environment.USE_SECOND_LEVEL_CACHE, "false" );
 	}
 
@@ -70,7 +68,9 @@
 	 * Odd as it may sound, EJB3 LockModeType.READ actually maps to the Hibernate LockMode.UPGRADE
 	 */
 	public void testLockModeTypeRead() {
-		// todo : add some protections here for databases which have issues with concurrent access...
+		if ( ! readCommittedIsolationMaintained( "ejb3 lock tests" ) ) {
+			return;
+		}
 
 		final String initialName = "lock test";
 		// set up some test data
@@ -135,8 +135,6 @@
 	 * a new Hibernate LockMode was added to support this behavior: {@link LockMode#FORCE}.
 	 */
 	public void testLockModeTypeWrite() {
-		// todo : add some protections here for databases which have issues with concurrent access...
-
 		final String initialName = "lock test";
 		// set up some test data
 		Session s1 = getSessions().openSession();