Chapter 6 Enterprise JavaBeans Overview

EAServer EJB support

EAServer can host Enterprise JavaBeans (EJB) components developed according to version 2.0, 1.1, or 1.0 of the Enterprise JavaBeans specification. EAServer supports session beans and entity beans with bean-managed persistence or container-managed persistence. EAServer uses CORBA 2.3 as the basis for the EJB component support, allowing interoperability with other client and component models and with CORBA-2.3-compliant ORBs from other vendors.

Running EJB components in EAServer

You can run Enterprise JavaBeans as EAServer components using any of these techniques:

Define EJB components in PowerJ, using wizards to define the interfaces and deploy the bean directly from PowerJ to EAServer. See the PowerJ documentation for more information.
Use Jaguar Manager to import an EJB-JAR file that contains the classes and deployment descriptors for one or more EJB components. Jaguar Manager defines components with properties matching the deployment descriptor settings.
Import compiled versions of a home interface, remote interface, implementation class, and (for entity beans) the primary key class. Jaguar Manager defines IDL interfaces for the interfaces and the primary key, and defines an EJB component with default settings. You can configure additional settings such as transaction attributes and database resource references using the Jaguar Manager Component Properties dialog box.
Define an EJB component from scratch in Jaguar Manager, using Jaguar Manager's IDL generation tools to define the home interface, remote interface, and primary key type. Jaguar Manager generates Java classes for the home and remote interfaces and primary key class, as well as a template for the implementation class.

EAServer also supports the Enterprise JavaBeans client model. You can generate EJB-style proxies for any IDL interface, and use the proxies to call methods on components that implement that interface.

EJB clients connecting to EAServer

EAServer also supports the Enterprise JavaBeans client model by generating EJB proxies and providing an EJB-compliant implementation of the JNDI NamingContext class. You can generate EJB-style proxies for any IDL interface (not just those associated with EJB components), and use the proxies to call methods on components that implement that interface. The NamingContext class can also be used in EJB components to instantiate home interfaces for intercomponent calls.

For more information

For information about	See this chapter
Creating, importing, and exporting EJB components.	Chapter 7, "Creating Enterprise JavaBeans Components"
Creating EJB clients, generating EJB stubs, instantiating home and remote interface proxies, managing transactions, and serializing and deserializing bean proxies.	Chapter 7, "Creating Enterprise JavaBeans Components"
Configuring container-managed persistence for entity beans and passivation of stateful session beans	Chapter 25, "Managing Persistent Component State"
Invoking non-EJB components from EJB clients and invoking EJB components from non-EJB clients, and using EAServer with EJB 2.0 containers from other vendors.	Chapter 9, "EAServer EJB Interoperability"