Configuring and administering

Documentation

Developing

This section provides a guide for creating deployment plans, in which Geronimo-specific configuration is accomplished via resource reference, dependencies and so on. It is organized in the following parts:

• Creating deployment plans for applications — This section summarizes how to develop Geronimo deployment plans for different Java EE 5 modules.
  • Creating deployment plans for Java Persistence API
  • Naming (JNDI) — This page describes how the Geronimo server puts the names of JCA objects and EJBs in the JNDI namespace so that clients may access them.
  • Creating deployment plans for enterprise applications — When an EAR consist of many sub modules, the deployment plans for all the sub modules can be provided in a single file named geronimo-application.xml.
  • Annotations — The Java EE 5 specifications also allows the usage of annotations directly in the Java code to mitigate the development burdens associated with creating Java EE 5 applications.
  • Configuring resources in the application scope
  • Creating deployment plans for EJB applications — Geronimo uses OpenEJB container for providing ejb services. An EJB application requires ejb-jar.xml as deployment descriptor and openejb-jar.xml as deployment plan.
  • Creating deployment plans for Java EE application clients — A Java EE client module requires application-client.xml as deployment descriptor and geronimo-application-client.xml as deployment plan.
  • Creating deployment plans for Web applications — A Web application requires web.xml as deployment descriptor and geronimo-web.xml as deployment plan.
• Creating deployment plans using the deployment plan wizard — The Plan Creator wizard available from the Geronimo Administration Console makes deployment easier by walking you through a sequence of steps to auto-generate the geronimo-web.xml for a given WAR file.
• Understanding deployment plans — Every module that you install in Geronimo, whether it is a service, application, resource, and so on, can be configured via a deployment plan.
  • persistence.xml
  • geronimo-application-client.xml — The Geronimo deployment plan for a Java EE application, which is usually packaged as a JAR file, is called "geronimo-application-client.xml".
  • openejb-jar.xml — Geronimo uses the OpenEJB container for providing EJB services. With the advent of Java EE, 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 via usage of the ejb-jar.xml file.
  • geronimo-web.xml — The Geronimo-specific deployment plan for a Web application, which is usually packaged as a WAR file, is called "geronimo-web.xml".
  • geronimo-ra.xml
  • geronimo-application.xml — The Geronimo deployment plan for an enterprise application, which is usually packaged as a EAR file, is called "geronimo-application.xml".