7.1 Overview of creating J2EE applications

Creating a J2EE application refers to the process of using an Enterprise Bean (EJB-JAR) and servlet created in an application development environment and a JSP (WAR) to create a J2EE application (EAR). In a J2EE application, you can also include resource adapters that you want to use in that J2EE application.

The following table describes the operations required for creating a J2EE application.

Table 7‒1: Operations to be executed for creating a J2EE application

Items to be executed	Contents	Reference
Importing the Enterprise Beans (EJB-JAR)	Operation required when the Enterprise Beans (EJB-JAR) are included in the configuration of the J2EE application. Import the Enterprise Beans into the J2EE server.	7.2.1
Importing the servlet and JSP (WAR)	Operations required when the servlets and JSPs (WAR) are included in the configuration of the J2EE application. Import the servlets and JSPs into the J2EE server.	7.2.2
Importing resource adapters (RAR files)	When resource adapters (RAR) are included in J2EE applications, import the included resource adapters into the J2EE server.	7.2.3
Creating a new J2EE application	Create an EAR file on the basis of the imported EJB-JAR and WAR files. Include RAR in J2EE applications as and when required.	7.2.4
Adding library JAR files to the J2EE application	Add the library JAR files (file extension is the lower case .jar) to the J2EE application.	7.2.5
Referencing the list of library JAR files	Reference the list of library JAR files included in the J2EE application.	7.2.6
Deleting the library JAR files from the J2EE application	Delete the library JAR files included in the J2EE application.	7.2.7
Setting a reference library in the J2EE application	Set the reference library in the J2EE application.	7.2.8
Property settings of J2EE applications	Set the properties for the created J2EE application.	Chapter 9
Executing J2EE applications	Execute the J2EE application for which setup is complete. Terminate the applications based on the operations.	Chapter 10

To create J2EE applications with cosminexus.xml, you include cosminexus.xml, created in advance, along with EJB-JAR and WAR files in J2EE applications, and then use.

The library JAR and reference library are common libraries and you can reference these libraries from each module of the J2EE application.

The library JAR and reference library have the following features:

• Library JAR

  • The J2EE application includes a JAR (file extension is the lower case .jar).

  • When used in multiple J2EE applications, a library JAR needs to be added in each J2EE application.

  • The library JAR cannot include a class file. To use a class file, the class file needs to be compiled in a JAR file format.

• Reference library

  • The reference library specifies the absolute path of the library file to be referenced.

  • When used in multiple J2EE applications, you can use the same reference library by simply specifying the same reference.

  • The reference library can handle JAR files as well as class files.

When including the following classes in a common library that can be referenced from each module in a J2EE application, you must use a library JAR to include the classes: classes coded in an ejb-jar.xml or web.xml file, methods (arguments, return values, and exceptions), classes^# that are loaded for reading annotation information, and classes required for the reference solution of the included classes. When these classes are used as a reference library, java.lang.NoClassDefFoundError or java.lang.ClassNotFoundException occurs when importing applications, and an attempt to acquire the annotation information fails (KDJE42380-W is output) or an attempt to import fails.

#

For details on the classes loaded for reading the annotation information, see 14.3 Classes to be loaded and the class path required for loading in the uCosminexus Application Server Common Container Functionality Guide.

To Page Top