Wiki Markup |
---|
{scrollbar} |
Excerpt | ||
---|---|---|
| ||
An EJB application require ejb-jar.xml as deployment descriptor and openejb-jar.xml as deployment plan. |
Geronimo uses OpenEJB container for providing ejb services. With the advent of Java EE 5, the ejb container services such as transaction management, security, life cycle management can be declared in the ejb class itself using annotations. However, the ejb deployment descriptor can still be provided through ejb-jar.xml
file. When both annotations and ejb-jar.xml
file are provided, the ejb-jar.xml
file takes precedence over the annotations. excerpt
The openejb-jar.xml
file contains deployment plan for ejb modules. In the openejb-jar.xml
file, the application deployer maps the security roles, ejb names, database resources, JMS resources, etc. declared in ejb-jar.xml
file to corresponding entities deployed in the server. In addition to that, if there are any ejb container specific configurations to be done, the required settings are configured as well here. If the ejb module depends on any third party libraries or other services running in the server, all these third party libraries and the services are specified in the openejb-jar.xml
file. Some ejb applications require class loading requirements different from the default class loading behavior. The openejb-jar.xml
file allows application deployer to configure this as well. There are many more configurations that could be done through openejb-jar.xml
file depending on the needs of the ejb application. The following sections briefly explain how openejb-jar.xml
file can be used to configure the ejb container and ejb applications.
...