org.openejb.test.stateful
Class StatefulBeanTxTests

java.lang.Object
  extended by junit.framework.Assert
      extended by org.openejb.test.NumberedTestCase
          extended by org.openejb.test.NamedTestCase
              extended by org.openejb.test.stateful.StatefulBeanTxTests
All Implemented Interfaces:
junit.framework.Test

public class StatefulBeanTxTests
extends NamedTestCase

[1] Should be run as the first test suite of the StatefulTestClients

Author:
David Blevins, Richard Monson-Haefel

Field Summary
protected  javax.ejb.Handle ejbHandle
           
protected  BeanTxStatefulHome ejbHome
           
protected  javax.ejb.HomeHandle ejbHomeHandle
           
protected  javax.ejb.EJBMetaData ejbMetaData
           
protected  BeanTxStatefulObject ejbObject
           
protected  java.lang.Integer ejbPrimaryKey
           
protected  javax.naming.InitialContext initialContext
           
static java.lang.String jndiEJBHomeEntry
           
 
Fields inherited from class org.openejb.test.NamedTestCase
testName
 
Fields inherited from class org.openejb.test.NumberedTestCase
standardPrefix
 
Constructor Summary
StatefulBeanTxTests()
           
 
Method Summary
 void BUG_test06_singleTransactionRollback()
          This test does work for the IntraVM Server, but it fails on the Remote Server.
protected  void setUp()
          Sets up the fixture, for example, open a network connection.
protected  void tearDown()
          Tears down the fixture, for example, close a network connection.
 void test01_EJBContext_getUserTransaction()
          11.6.1 Bean-managed transaction demarcation
 void test02_java_comp_UserTransaction()
          11.6.1 Bean-managed transaction demarcation
 void test05_singleTransactionCommit()
           
 void TODO_test03_EJBContext_setRollbackOnly()
          11.6.1 Bean-managed transaction demarcation
 void TODO_test04_EJBContext_getRollbackOnly()
          11.6.1 Bean-managed transaction demarcation
 void TODO_test07_serialTransactions()
          11.6.1 Bean-managed transaction demarcation
 void TODO_test08_nestedTransactions()
          11.6.1 Bean-managed transaction demarcation
 void TODO_test09_methodSpanningTransactions()
          11.6.1 Bean-managed transaction demarcation
 void TODO_test10_scenario1_NoneNone()
          11.6.1 Bean-managed transaction demarcation
 void TODO_test11_scenario2_T1None()
          11.6.1 Bean-managed transaction demarcation
 void TODO_test12_scenario3_NoneT2()
          11.6.1 Bean-managed transaction demarcation
 void TODO_test13_scenario4_T1T2()
          11.6.1 Bean-managed transaction demarcation
 
Methods inherited from class org.openejb.test.NamedTestCase
name
 
Methods inherited from class org.openejb.test.NumberedTestCase
countTestCases, createTest, createTestName, removePrefix, removePrefix, run, run, runTestMethod, toString
 
Methods inherited from class junit.framework.Assert
assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, fail, fail, failNotEquals, failNotSame, failSame
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

jndiEJBHomeEntry

public static final java.lang.String jndiEJBHomeEntry
See Also:
Constant Field Values

ejbHome

protected BeanTxStatefulHome ejbHome

ejbObject

protected BeanTxStatefulObject ejbObject

ejbMetaData

protected javax.ejb.EJBMetaData ejbMetaData

ejbHomeHandle

protected javax.ejb.HomeHandle ejbHomeHandle

ejbHandle

protected javax.ejb.Handle ejbHandle

ejbPrimaryKey

protected java.lang.Integer ejbPrimaryKey

initialContext

protected javax.naming.InitialContext initialContext
Constructor Detail

StatefulBeanTxTests

public StatefulBeanTxTests()
Method Detail

setUp

protected void setUp()
              throws java.lang.Exception
Sets up the fixture, for example, open a network connection. This method is called before a test is executed.

Overrides:
setUp in class NumberedTestCase
Throws:
java.lang.Exception

tearDown

protected void tearDown()
                 throws java.lang.Exception
Tears down the fixture, for example, close a network connection. This method is called after a test is executed.

Overrides:
tearDown in class NumberedTestCase
Throws:
java.lang.Exception

test01_EJBContext_getUserTransaction

public void test01_EJBContext_getUserTransaction()
11.6.1 Bean-managed transaction demarcation

The Container must make the javax.transaction.UserTransaction interface available to the enterprise bean?s business method via the javax.ejb.EJBContext interface and under the environment entry java:comp/UserTransaction. When an instance uses the javax.trans-action. UserTransaction interface to demarcate a transaction, the Container must enlist all the resource managers used by the instance between the begin() and commit()?or rollback()? methods with the transaction. When the instance attempts to commit the transaction, the Container is responsible for the global coordination of the transaction commit.

--------------------------------------------------------

Check that a javax.transaction.UserTransaction can be obtained from the javax.ejb.EJBContext


test02_java_comp_UserTransaction

public void test02_java_comp_UserTransaction()
11.6.1 Bean-managed transaction demarcation

The Container must make the javax.transaction.UserTransaction interface available to the enterprise bean?s business method via the javax.ejb.EJBContext interface and under the environment entry java:comp/UserTransaction. When an instance uses the javax.trans-action. UserTransaction interface to demarcate a transaction, the Container must enlist all the resource managers used by the instance between the begin() and commit()?or rollback()? methods with the transaction. When the instance attempts to commit the transaction, the Container is responsible for the global coordination of the transaction commit.

--------------------------------------------------------

Check that a javax.transaction.UserTransaction can be obtained from the environment entry java:comp/UserTransaction


TODO_test03_EJBContext_setRollbackOnly

public void TODO_test03_EJBContext_setRollbackOnly()
11.6.1 Bean-managed transaction demarcation

The Container must throw the java.lang.IllegalStateException if an instance of a bean with bean-managed transaction demarcation attempts to invoke the setRollbackOnly() or getRollbackOnly() method of the javax.ejb.EJBContext interface.

--------------------------------------------------------

Test that setRollbackOnly() throws a java.lang.IllegalStateException


TODO_test04_EJBContext_getRollbackOnly

public void TODO_test04_EJBContext_getRollbackOnly()
11.6.1 Bean-managed transaction demarcation

The Container must throw the java.lang.IllegalStateException if an instance of a bean with bean-managed transaction demarcation attempts to invoke the setRollbackOnly() or getRollbackOnly() method of the javax.ejb.EJBContext interface.

--------------------------------------------------------

Test that getRollbackOnly() throws a java.lang.IllegalStateException


test05_singleTransactionCommit

public void test05_singleTransactionCommit()

BUG_test06_singleTransactionRollback

public void BUG_test06_singleTransactionRollback()
This test does work for the IntraVM Server, but it fails on the Remote Server. For some reason, when the RollbackException is sent to the client, the server blocks.


TODO_test07_serialTransactions

public void TODO_test07_serialTransactions()
11.6.1 Bean-managed transaction demarcation

The Container must allow the enterprise bean instance to serially perform several transactions in a method.


TODO_test08_nestedTransactions

public void TODO_test08_nestedTransactions()
11.6.1 Bean-managed transaction demarcation

When an instance attempts to start a transaction using the begin() method of the javax.transaction.UserTransaction interface while the instance has not committed the previous transaction, the Container must throw the javax.transaction.NotSupportedException in the begin() method.


TODO_test09_methodSpanningTransactions

public void TODO_test09_methodSpanningTransactions()
11.6.1 Bean-managed transaction demarcation

In the case of a stateful session bean, it is possible that the business method that started a transaction completes without committing or rolling back the transaction. In such a case, the Container must retain the association between the transaction and the instance across multiple client calls until the instance commits or rolls back the transaction. When the client invokes the next business method, the Container must invoke the business method in this transaction context.


TODO_test10_scenario1_NoneNone

public void TODO_test10_scenario1_NoneNone()
11.6.1 Bean-managed transaction demarcation

The actions performed by the Container for an instance with bean-managed transaction are summarized by the following table. T1 is a transaction associated with a client request, T2 is a transaction that is cur-rently associated with the instance (i.e. a transaction that was started but not completed by a previous business method).

 =========================================================================
 Container?s actions for methods of beans with bean-managed transaction
 =========================================================================

            |      IF     |          AND             |          THEN
  scenario  |   Client?s  | Transaction currently    | Transaction associated
            | transaction | associated with instance | with the method is
 ___________|_____________|__________________________|________________________
            |             |                          |
    1       |  none       |  none                    |  none
 ___________|_____________|__________________________|________________________
            |             |                          |
    2       |  T1         |  none                    |  none
 ___________|_____________|__________________________|________________________
            |             |                          |
    3       |  none       |  T2                      |  T2
 ___________|_____________|__________________________|________________________
            |             |                          |
    4       |  T1         |  T2                      |  T2
 ___________|_____________|__________________________|________________________
 

If the client request is not associated with a transaction and the instance is not associated with a transaction, the container invokes the instance with an unspecified transaction context.

--------------------------------------------------------

Test scenario 1: none none
If the client's transaction is none and the transaction currently associated with instance none then the transaction associated with the method is none.


TODO_test11_scenario2_T1None

public void TODO_test11_scenario2_T1None()
11.6.1 Bean-managed transaction demarcation

The actions performed by the Container for an instance with bean-managed transaction are summarized by the following table. T1 is a transaction associated with a client request, T2 is a transaction that is cur-rently associated with the instance (i.e. a transaction that was started but not completed by a previous business method).

 =========================================================================
 Container?s actions for methods of beans with bean-managed transaction
 =========================================================================

            |      IF     |          AND             |          THEN
  scenario  |   Client?s  | Transaction currently    | Transaction associated
            | transaction | associated with instance | with the method is
 ___________|_____________|__________________________|________________________
            |             |                          |
    1       |  none       |  none                    |  none
 ___________|_____________|__________________________|________________________
            |             |                          |
    2       |  T1         |  none                    |  none
 ___________|_____________|__________________________|________________________
            |             |                          |
    3       |  none       |  T2                      |  T2
 ___________|_____________|__________________________|________________________
            |             |                          |
    4       |  T1         |  T2                      |  T2
 ___________|_____________|__________________________|________________________
 

If the client is associated with a transaction T1, and the instance is not associated with a transaction, the container suspends the client?s transaction association and invokes the method with an unspecified transaction context. The container resumes the client?s transaction association (T1) when the method completes.

--------------------------------------------------------

Test scenario 2: T1 none


TODO_test12_scenario3_NoneT2

public void TODO_test12_scenario3_NoneT2()
11.6.1 Bean-managed transaction demarcation

The actions performed by the Container for an instance with bean-managed transaction are summarized by the following table. T1 is a transaction associated with a client request, T2 is a transaction that is cur-rently associated with the instance (i.e. a transaction that was started but not completed by a previous business method).

 =========================================================================
 Container?s actions for methods of beans with bean-managed transaction
 =========================================================================

            |      IF     |          AND             |          THEN
  scenario  |   Client?s  | Transaction currently    | Transaction associated
            | transaction | associated with instance | with the method is
 ___________|_____________|__________________________|________________________
            |             |                          |
    1       |  none       |  none                    |  none
 ___________|_____________|__________________________|________________________
            |             |                          |
    2       |  T1         |  none                    |  none
 ___________|_____________|__________________________|________________________
            |             |                          |
    3       |  none       |  T2                      |  T2
 ___________|_____________|__________________________|________________________
            |             |                          |
    4       |  T1         |  T2                      |  T2
 ___________|_____________|__________________________|________________________
 

If the client request is not associated with a transaction and the instance is already associated with a transaction T2, the container invokes the instance with the transaction that is associated with the instance (T2). This case can never happen for a stateless Session Bean.

--------------------------------------------------------

Test scenario 3: none T2


TODO_test13_scenario4_T1T2

public void TODO_test13_scenario4_T1T2()
11.6.1 Bean-managed transaction demarcation

The actions performed by the Container for an instance with bean-managed transaction are summarized by the following table. T1 is a transaction associated with a client request, T2 is a transaction that is cur-rently associated with the instance (i.e. a transaction that was started but not completed by a previous business method).

 =========================================================================
 Container?s actions for methods of beans with bean-managed transaction
 =========================================================================

            |      IF     |          AND             |          THEN
  scenario  |   Client?s  | Transaction currently    | Transaction associated
            | transaction | associated with instance | with the method is
 ___________|_____________|__________________________|________________________
            |             |                          |
    1       |  none       |  none                    |  none
 ___________|_____________|__________________________|________________________
            |             |                          |
    2       |  T1         |  none                    |  none
 ___________|_____________|__________________________|________________________
            |             |                          |
    3       |  none       |  T2                      |  T2
 ___________|_____________|__________________________|________________________
            |             |                          |
    4       |  T1         |  T2                      |  T2
 ___________|_____________|__________________________|________________________
 

If the client is associated with a transaction T1, and the instance is already associated with a transaction T2, the container suspends the client?s transaction association and invokes the method with the transaction context that is associated with the instance (T2). The container resumes the client?s transaction association (T1) when the method completes. This case can never happen for a stateless Session Bean.

--------------------------------------------------------

Test scenario 4: T1 T2



Copyright © 1999-2011 OpenEJB. All Rights Reserved.