Summary

In this chapter, you explored:

• The different J2EE-deployable modules for Geronimo

• The mandatory J2EE deployment descriptors that must be included in the module

• The optional Geronimo-specific deployment plans that can be included during deployment

The mandatory J2EE deployment descriptors have specific names and must be placed in specific location within the module archive. Their contents are well specified via XML schemas.

The optional Geronimo-specific deployment plans can be placed inside the deployed module or external to the module. When placed internally, they must be at a specific location with a specific name in order for Geronimo to find them. The contents of Geronimo-specific deployment plans are regulated via XML schemas.

Once a module is deployed into Geronimo, it is referenced using a module ID. This module ID can be specified explicitly using a Geronimo-specific deployment plan for the module. By default, Geronimo will use the base name of the archive file and a timestamp to create the default module ID.

Upcoming chapters will guide you through the deployment of all the different types of deployable modules. You will get a chance to explore and work with many deployment descriptors and deployment plans in the examples within these chapters.