Java Reference
In-Depth Information
Java EE 5.0 made the deployment descriptor optional, even in the EAR. This is a departure
from previous versions of Java EE, where it was mandatory. The Java EE 5.0-compliant
application servers deploy by performing automatic detection based on a standard naming
convention or reading the content of archives. For more information on these conventions,
see . Next, we'll
take a look at how application servers deploy an EAR module.
13.1.2. Loading a Java EE module
During the deployment process, the application server determines the module types, valid-
ates them, and takes appropriate steps so that the application is available to users. Although
all application servers have to accomplish these goals, it's up to the individual vendor as to
exactly how to implement it. One area where server implementations stand out is in how
fast they can deploy the archive.
Although vendors are free to optimize their specific implementation, they all follow the
specification's rules when it comes to what is required to be supported and in what order
the loading occurs. This means that your application server will use the algorithm from fig-
ure 13.1 when attempting to load the EAR file that contains modules or archives from table
13.1 .
Search WWH ::

Custom Search