Programming Restrictions

The EJB 1.1 specification contains the following programming restrictions, which you must follow when implementing the methods of an EJB class:

• An EJB should not start new threads nor attempt to terminate the running thread. In the current release if an EJB starts a new thread no exception is thrown, but the application behavior becomes unpredictable due to interactions with local thread objects in the ORB.

• An EJB is not allowed to use thread synchronization primitives.

• An EJB can only use the javax.Transaction.UserTransaction interface to demarcate transactions.

• An EJB is not allowed to change its java.security.Identity. Any attempt to do so results in the java.security.SecurityException being thrown.

• An EJB is not allowed to use JDBC commit and rollback methods nor to issue direct SQL commit or rollback commands using SQLJ or JDBC.

The 1.1 EJB specification states that "an EJB is not allowed to use read/write static fields. Using read-only static fields is allowed. Therefore, all static fields must be declared as final." This is not a restriction for Oracle8i.

---