Java™ Application Development on Linux - Dator

23.2 Lend Me Your EAR: Enterprise Packaging and Deployment507Example 23.1 Contents of a sample EAR file$ jar -tvf budgetpro.ear0 Wed May 19 05:58:02 CDT 2004 META-INF/110 Wed May 19 05:58:00 CDT 2004 META-INF/MANIFEST.MF295 Wed May 19 05:58:00 CDT 2004 META-INF/application.xml11498 Wed May 19 05:58:02 CDT 2004 budgetpro.jar12626 Wed May 19 05:58:02 CDT 2004 budgetpro.war$Table 23.1 Files inside an EAR archiveNamebudgetpro.jarbudgetpro.warMANIFEST.MFapplication.xmlMETA-INFTypeJARWARtextXMLdirectoryContentThe EJB-JAR file—the JAR file that contains our EJB.The Web application with servlet and JSP files.A standard JAR manifest; at a minimum, it gives theversion number of the JAR file format—for example,Manifest-Version: 1.0.The deployment descriptor, an XML description ofwhat’s what.A directory with other files.The plain files that appear in the META-INF directory are simple. TheMANIFEST.MF file is like any JAR manifest and can contain simply the JARversion number:Manifest-Version: 1.0The application.xml file is shown in Example 23.2Two JAR files are mentioned in this XML description file. This tells thecontainer that we have two modules, an EJB and a Web application. The Webmodule also defines a context root, which is the portion of the URL pathnamethat is intended to direct requests to this Web application. For example, if yourhost is www.bighost.com, then the context root of /budgetpro means thatthe URL you will use to access the Web application in this EAR iswww.bighost.com/budgetpro/ followed by whatever other filename youmight need to append, such as a JSP file—or, if left blank, the defaultindex.html file.