Security Changes

Component Interoperability

When you develop a distributed application, you want the components to be as independent as possible. A component developer shouldn't be concerned about the location of other components or any details of their implementation. EJB 2.0 helps achieve this goal by specifying an interoperability protocol based on CORBA/IIOP. The goal is to allow session and entity beans developed and deployed into one vendor's EJB container to be accessible to other applications running in a different vendor's J2EE application server. These applications can include other EJBs, servlets, JSPs, and standalone applications. By basing the interoperability requirement on CORBA, access from CORBA clients written in languages such as C++ or COBOL is also simplified. You can now develop your EJBs without concern for the vendor of the server used to deploy them and be guaranteed interoperability with applications running inside other compliant servers.

For more information on the new interoperability requirements, see Chapter 20, "Distribution and EJB Interoperability," p. 511 .