THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Wiki Markup |
|---|
{scrollbar} |
| Anchor | ||||
|---|---|---|---|---|
|
Every service, application or resource in Geronimo is configured with an xml deployment plan. Deployment plans are the Geronimo version of the J2EE deployment descriptors. They are still XML files based on XML schemas containing the configuration details for a specific application module. Via the deployment plans you can not only deploy application modules but also other configurations such as a security realm,see the Create new database pools and LDAP Realm sections as some examples.This article is organized into the following sections :
Apache Geronimo v1.1 deployment plans
The following table illustrates the deployment descriptors name and file location for both standard J2EE and Apache Geronimo specific.
File | Standard Deployment Descriptors in the J2EE specification | Apache Geronimo specific Deployment plan |
|---|---|---|
Web Application Archive (WAR) | web.xml under the WEB-INF directory | geronimo-web.xml |
Enterprise Web application archive (EAR) | application.xml | geronimo-application.xml |
J2EE Connector resources archive (RAR) | ra.xml | geronimo-ra.xml |
J2EE client application archive (JAR) | client.xml | geronimo-application-client.xml |
JAR containing EJBs | ejb-jar.xml under the META-INF directory | openejb-jar.xml |
Detailed deployment plans
Each deployment plans will be discussed separately and are available at the following locations: -
- geronimo-web.xml
- geronimo-application.xml
- geronimo-ra.xml
- geronimo-application-client.xml
- openejb-jar.xml