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
- Annotations
- Configuring resources in the application scope
- Creating deployment plans for EJB applications
- 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
- 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.
Bookmark this on Delicious
Digg this
