What's different in Enterprise JavaBeans 1.1?

Richard Monson-Haefel

The most significant changes are listed below:

  • Entity bean support, both container- and bean-managed persistence, is required.
  • Java RMI-IIOP argument and reference types must be supported, but any protocol can still be used including IIOP, JRMP, HTTP, or a proprietary protocol. In other words, the client API must support the Java RMI-IIOP programming model for portability, but the underlying protocol can be anything.
  • The javax.ejb.depoyment package has been dropped in favor of a XML based deployment descriptor
  • Declarative security authorization (access control) has changed to be more role driven. Also the runAs declarations have been eliminated.
  • Declarative isolation levels are no longer available. Isolation levels are now managed explicitly through JDBC (BMP), the database or other vendor specific mechanisms.
  • The bean-container contract as been enhanced to include a default JNDI context for accessing properties, resources, (JDBC, JMS, etc), and other beans.
  • The basic EJB roles have been expanded and redefined to better separate responsibilities involved in the development, deployment, and hosting of enterprise beans.

Available On-line: A comprehensive examination of the changes made in EJB 1.1
This material is from "Appendix D" of the book Enterprise JavaBeans (O'Reilly 1999)

Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

About | Sitemap | Contact