EJB.C.5 Changes Since EBJ.1.1 Draft 1

This sections lists the changes since EJB 1.1 Draft 1.

Allow use of the Java 2 java.util.Collection interfaces for the result of entity finder methods .

Defining the FinderException in the finder methods of the home interface is mandatory now.

Cleanup of the exception specification, including minor changes from EJB 1.0 summarized in Section EJB.12.6.

The scope of the EJB specification for managing transaction isolation levels was reduced to sessions with bean-managed transaction demarcation. The current EJB specification does not have any API for managing transaction isolation for beans with container-managed transaction demarcation (note that all entity beans fall into this category).

Eliminated the stateless-session element in the XML DTD. Now the session element is used to describe both the stateful and stateless session beans.

Added an optional description element to the method element. The intention is to allow tools to display the description of the method.

Clarified that the enterprise bean class may have superclasses, and that the business methods and the various container callbacks can be implemented in the enterprise bean class, or in any of its superclasses.

Fixed the example that illustrates the use of handles for session objects. Serialized handles are not guaranteed to be deserializable in a different system, and therefore they cannot be e-mailed.

Updated the Overview chapter.

Allowed deferring the specification of the primary key class for all entities (not only for those with container-managed persistence as it was the case in Draft 1).

Allow enterprise beans to print. The container must grant the permission to the enterprise beans to queue printer job.

The setRollbackOnly() and getRollbackOnly() methods of the EJBContext object must not be used by enterprise beans with bean-managed transaction demarcation. There is no need for these beans to use these methods.