EJB.C.2 Changes Since Release 0.9

Renamed javax.ejb.InstanceContext to javax.ejb.EJBContext .

Fixed bugs in the javadoc of the javax.ejb.EntityContext interface.

Combined the state diagrams for non-transactional and transactional session beans into a single diagram.

Added the definition of the restrictions on using transaction scopes with a session bean (a session bean can be only in a single transaction at a time).

Allowed the enterprise bean's class to implement the enterprise bean's remote interface. This change was requested by reviewers to facilitate migration of existing code written in the Java programming language to Enterprise JavaBeans.

Removed the javax.ejb.EJBException from the specification, and replaced its use by the standard java.rmi.RemoteException . This change was necessary because of the previous change that allows the enterprise bean class to implement its remote interface.

Changed some rules regarding exception handling.

Renamed to the javax.jts.CurrentTransaction interface to javax.jts.UserTransaction to avoid confusion with the org.omg.CosTransactions.Current interface. The javax.jts.UserTransaction interface defines the subset of operations that are "safe" to use at the application level, and can be supported by the majority of the transaction managers used by existing platforms.

Added specification for TX_BEAN_MANAGED transactions.

Made the isolation levels supplied in the deployment descriptor applicable also to session beans and entities with bean-managed persistence.

Renamed the destroy() methods to remove() . This change was requested by several reviewers who pointed out the potential for name space collisions in their implementations .

Added the create arguments to the ejbPostCreate method. This simplifies the programming of an entity bean that needs the create arguments in the ejbPostCreate method (previously, the bean would have to save these arguments in the ejbCreate method).

Added restrictions on the use of per-method deployment attributes.

Added javax.ejb.EJBMetaData to the examples, and added the generation of the class that implements this interface as a requirement for the container tools.

Added the getRollbackOnly method to the javax.ejb.EJBContext interface. This method allows an instance to test if the current transaction has been marked for rollback. The test may help the enterprise bean to avoid fruitless computation after it caught an exception.

We removed the placeholder Appendix for examples. We will provide examples on the Enterprise JavaBeans architecture web site rather than in this document.