Page History

...

Please observe how the JEE 5 resource names and ejb names in ejb-jar.xml and web.xml are mapped to actual resources deployed in the server through geronimo-application.xml.

As we can observe from the geronimo-application.xml, the deployment plans for web and ejb modules are wrapped in <module> .... </module> elements. The xml elements used to provide deployment plan for the web module are from the schema http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1^{Image Added} which is the schema for geronimo-web.xml. Similarly, the xml elements used to provide ejb deployment plan are from the schema http://openejb.apache.org/xml/ns/openejb-jar-2.2^{Image Added} which is the schema for openejb-jar.xml. Hence, geronimo-application.xml barrows elements from all other schemas to provide deployment plan for its sub modules.
Also, observe that, in the geronimo-application.xml, along with moduleId configuration for ear, the moduleId configuration for both web and ejb modules are provided. If the above ear file deployed on the server and the configurations are listed, the following output is displayed on the console.

C:\Geronimo-2.1\bin>deploy.bat --user system --password ma
nager list-modules
Using GERONIMO_BASE:   C:\Geronimo-2.1
Using GERONIMO_HOME:   C:\Geronimo-2.1
Using GERONIMO_TMPDIR: var\temp
Using JRE_HOME:        C:\sun\jre
Found 92 modules
  + Order/OrderEAR/5.0/car
      `-> OrderWEB.war
      `-> OrderEJB.jar
  + console.dbpool/OrderDS/1.0/rar
 

The moduleId Order/OrderEAR/5.0/car is the configuration the Order.ear.