Get the app out; Discover the ins and outs of J2EE application assembly and deployment

• Published in: Java world p. 1
• Main Author: Chang Sau Sheong
• Format: Magazine Article
• Language: English
• Published: San Francisco Foundry 19.01.2001
• ISSN: 1091-8906; 1091-8906

J2EE applications are applications written using the J2EE platform and deployed on a J2EE application server. They are composed of one or more J2EE components (classes developed based on the J2EE platform) and a J2EE application deployment descriptor. The deployment descriptor lists the application's components as modules. A J2EE module represents a J2EE application's basic unit of composition. You package a J2EE application using the JAR file format into a file with an .ear extension. A minimal J2EE application package will contain only J2EE modules and the application deployment descriptor. Larger J2EE application packages may also include libraries referenced by J2EE modules, help files, and documentation to aid the deployer and other interested parties. We have covered the internals of J2EE applications, as well as the basic mechanics of deploying them by hand (or by Ant). J2EE is a consolidating platform for all Java-based enterprise specifications such as EJB, servlet, JSP, and so on. J2EE applications combine one or more J2EE modules, which can be an EJB, a Web application, or a Java client (either application or applet). A J2EE application is archived into a EAR file for deployment, although J2EE modules can deployable separately. We also learned the creation process for the various archive files.