Creating deployment plans

Creating deployment plans using the deployment plan wizard

This section summarizes how to develop Geronimo deployment plans for different Java EE 5 modules.

• 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 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.
• 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 Java Persistence API
• Creating deployment plans for Web applications — A Web application requires web.xml as deployment descriptor and geronimo-web.xml as deployment plan.
  • Providing container specific settings for your Web application
• 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.
  • Client JNDI Names
  • Datasource, ConnectionFactory, MDB and JPA Naming
  • EJB naming
  • Global JNDI
  • JNDI environment references