Wiki Markup |
---|
{scrollbar} |
Excerpt |
---|
An enterprise application archive (EAR) can consist of several application modules. |
Every module that you install in Geronimo, whether it is a service, application, resource, and so on, can be configured via a deployment plan. |
web.xml
, application.xml
, and so on. In some cases, the deployment descriptor is all that is required to install a module into a Geronimo server. However, in many cases, server-specific configuration is required when modules are installed. This server-specific configuration is accomplished by using Geronimo deployment plans.Geronimo deployment plans can be packaged along with the application or specified externally at deployment time. If provided during deployment, this plan will overwrite any other Geronimo specific deployment plan provided with the application.
To package the deployment plans in you application you have to follow some naming conventions and place the file in a specific directory within your packaged application. For example, in a Web application you would include the geronimo-web.xml under the /WEB-INF
directory, same place where you are also providing the web.xml descriptor, all within the WAR. For an enterprise application you would include the geronimo-application.xml under the /META-INF
directory, same place where you are also providing the application.xml descriptor, all within the WAR.
Java EE Deployment Plans
...