Summary

This chapter describes how to deploy EJB modules into Geronimo. EJB modules are bundled in JAR files with an embedded ejb-jar.xml deployment descriptor. This J2EE deployment descriptor describes all the EJBs that are in the bundle. It also describes references to external resources that the EJBs depend on. This can include other EJBs, resource adapters (such as JDBC connectors and JMS connection factories) and also container-managed resources (such as message destinations and security roles).

Simple EJB modules that are created to be deployed in a known environment can occasionally be deployed to Geronimo without additional Geronimo-specific deployment plan. In most cases, however, the creation of openejb-jar.xml is required. This Geronimo-specific deployment plan maps the references of the EJB module(s) to actual known resources in the container.

The intelligence built into the container for locating resources significantly simplifies the creation of the deployment plan. For example, external EJB references are matched by the container based on the home and remote (or local) interfaces by the container.

Geronimo also has built-in support for JavaMail, and provides backward compatibility with fat-client applications with a client application container.

Chapter 13 explores the deployment of JDBC resources in Geronimo.