Java Reference
In-Depth Information
The ActionBazaar application contains an EJB-JAR module, a web module, a JAR contain-
ing helper classes, and an application client module. The file structure of the EAR module
for ActionBazaar looks like this:
META-INF/application.xml
actionBazaar-ejb.jar
actionBazaar.war
actionBazaar-client.jar
lib/actionBazaar-commons.jar
Here application.xml is the deployment descriptor that describes the standard Java EE mod-
ules packaged in each EAR file. The contents of application.xml look something like the
following listing.
Listing 13.1. ActionBazaar EAR module deployment descriptor
If you review the EAR module deployment descriptor in this listing, you'll see that it ex-
plicitly identifies each of the artifacts as a specific type of module. The EJB module
has the EJBs with your application's business logic. The web module is the web-based
version your application. The application client module is another version of your ap-
plication, such as a thick-client GUI. When you deploy this EAR to an application server,
the application server uses the information in the deployment descriptor to deploy each of
the module types.
