...
An enterprise application archive (EAR
) can consist of many sub modules. The sub modules can be web modules (WAR
), ejb modules (JAR
), resource adapter modules (RAR
) or application client modules (jar
). When an EAR
consist of many sub modules, the deployment plans for all the sub modules can be provided in a single file named geronimo-application.xml
. This single file contains the deployment details of each of the sub modules of the EAR
. Alternatively, each of the sub modules can package its corresponding deployment plan file within itself. However, the preferable way is to provide a single deployment plan through geronimo-application.xml
for all the sub modules. This mechanism provides flexibility of allowing us to modify the deployment configuration for all modules through a single file. In this section, we explore EAR
deployment plan and understand what it contains.
Note |
---|
There are 3 places a deployment plan (partial plan ) can be associated for with an ear, and they are used in this order: 1. external plan So, anything in an external plan takes precedence over bits in (2) or (3) configuring the same module. Anything in (2) takes precedence over a module level plan. If a module level plan is missing from (1) its looked for in (2),then (3); if missing from (1) and (2), then its looked for in the module (3). There is no attempt to merge plans from these different locations: e.g. if there's something in (1) for a module, any other plans are ignored. |
...