Author: manaRH Date: 2012-07-31 09:37:28 -0400 (Tue, 31 Jul 2012) New Revision: 15010 Modified: branches/enterprise/JBPAPP_5_0/src/test/integration/src/org/jboss/seam/test/integration/FactoryLockTest.java Log: JBPAPP-9391 enabled interleavingFactories test and disabled sameFactoryLock test Modified: branches/enterprise/JBPAPP_5_0/src/test/integration/src/org/jboss/seam/test/integration/FactoryLockTest.java =================================================================== --- branches/enterprise/JBPAPP_5_0/src/test/integration/src/org/jboss/seam/test/integration/FactoryLockTest.java 2012-07-31 13:24:28 UTC (rev 15009) +++ branches/enterprise/JBPAPP_5_0/src/test/integration/src/org/jboss/seam/test/integration/FactoryLockTest.java 2012-07-31 13:37:28 UTC (rev 15010) @@ -46,7 +46,7 @@ thread.join(); } - assert !exceptionOccured; + Assert.assertEquals(exceptionOccured, false); } @@ -75,7 +75,8 @@ } // This test is the same as factoryLock test, except it uses the same factory in both threads. - @Test + // This is more like incorrect usage, EJB spec says that concurrent client access is invalid. + @Test(enabled=false) public void sameFactoryLock() throws Exception { @@ -99,7 +100,8 @@ // Test the behavior of two components using factories of each other. // Skip the test, as it causes deadlock. - @Test(enabled=false) + //@Test(enabled=false) + @Test public void interleavingFactories() throws Exception {