THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Excerpt | ||
|---|---|---|
| ||
This section summarizes how to develop Geronimo deployment plans for different Java EE 5 modules. |
An enterprise application archive (EAR) can consist of several application modules. The application modules can be several web application archives (WAR) , EJB modules (JAR), application client modules (JAR) or resource archive modules (RAR). User can either deploy these modules individually or bundle them into a single EAR file and deploy that file.
When deployed individually, each application module should accompany a Geronimo deployment plan to map declared resources names, ejb names, security roles, JMS roles (if any) to actual resources in the server. The Geronimo deployment plans also contain any Geronimo specific settings and configurations. When deployed as a single bundle (EAR), user can create a single Geronimo deployment plan accomplish to perform all the mappings/settings and configurations.
The following table summarizes different Java EE 5 modules and corresponding Geronimo deployment plans accompany them.
JEE module | JEE deployment descriptor (DD) | Geronimo deployment plan |
|---|---|---|
web application archive (WAR) | | |
EJB application archive (JAR) | | |
resource adapter archive (RAR) | | |
enterprise application archive (EAR) | | |
enterprise application client archive (JAR) | |
This section is organized as follows:
| Children Display | |||||
|---|---|---|---|---|---|
| |||||
|