THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Wiki Markup |
|---|
{scrollbar} |
Every "asset" you install in Geronimo, whether it is a service, application, resource, etc., it is configured via a deployment plan. JEE specification let's part of the configuration of such assets to be done by server specific deployment plans in addition to the standard deployment descriptors such as web.xml, application.xml, etc.
JEE specification also let's you use Annotations where you add resource references, dependencies, etc. directly in the code. Geronimo provides a Plan Creator wizard that automatically generates the necessary deployment plans based on the standard deployment descriptors and annotations.
| Table of Contents |
|---|
Applications
Depending on the type of application you are deploying you will need a different type of deployment plan. The following table illustrates the standard JEE deployment descriptors as well as those specific to Apache Geronimo.
File | Standard JEE deployment descriptors | Apache Geronimo specific Deployment plan |
|---|---|---|
Web Application Archive (WAR) | web.xml | 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 | openejb-jar.xml |
geronimo-web.xml
geronimo-application.xml
geronimo-ra.xml
geronimo-application-client.xml
openejb-jar.xml
Configurations
Connection pools
Security
| Excerpt |
|---|
This section provides a guide for creating deployment plans, in which Geronimo-specific configuration is accomplished via resource reference, dependencies and so on. |
| Children Display | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...