JavaServer Pages and Servlet Applications

For simple J2EE applications without EJB, it is common to package the application in an Enterprise Archive (EAR) file made up of various J2EE application component archives as Figure 9-2 shows.

Figure 9-2 Packaging a J2EE JSP or Servlet Application Without EJB

Description of "Figure 9-2 Packaging a J2EE JSP or Servlet Application Without EJB"

The component archives with TopLink dependencies include:

• TopLink Domain JAR

TopLink Domain JAR

The domain JAR contains the TopLink files and domain objects required by the application, including:

• sessions.xml File

• project.xml File (or the compiled Project class file if you are not using XML files for deployment)

• The mapped classes required by the application, in a fully-resolved directory structure

When you create the JAR file, the JAR building utility automatically creates a directory structure within the JAR. Ensure that the sessions.xml file and the project.xml file (or project.class file) appear at the root of the JAR file. Also ensure that the class directory structure starts at the root of the JAR.

If you do not store the project.xml or sessions.xml files at the root of the JAR file, see "Packaging With TopLink Metadata File Resource Paths".