Java Reference
In-Depth Information
FIGURE 1-6. EAR File Structure
The two types of deployment descriptors are Java EE and runtime. A
Java EE deployment
descriptor
is defined by a Java EE specification and can be used to configure deployment
settings on any Java EE-compliant implementation. A
runtime deployment descriptor
is used to configure Java EE implementation-specific parameters. For example, the
GlassFish Server runtime deployment descriptor contains such information as the context
root of a web application, as well as GlassFish Server implementation-specific parameters,
such as caching directives. The GlassFish Server runtime deployment descriptors are
named
glassfish-
moduleType
.xml
and are located in the same
META-INF
direct-
ory as the Java EE deployment descriptor.
A
Java EE module
consists of one or more Java EE components for the same container
type and, optionally, one component deployment descriptor of that type. An enterprise
bean module deployment descriptor, for example, declares transaction attributes and se-
curity authorizations for an enterprise bean. A Java EE module can be deployed as a stand-
alone module.
Java EE modules are of the following types:
• EJB modules, which contain class files for enterprise beans and, optionally, an EJB
deployment descriptor. EJB modules are packaged as JAR files with a
.jar
ex-
tension.
