Skip Headers

Oracle TopLink Developer's Guide 10g Release 3 (10.1.3) B13593-01 |
| Home | Solution Area | Contents | Index

Previous | Next |

# Java Applications

For non-J2EE Java applications, it is common to package the application in a single JAR file as Figure 9-1 shows.

Figure 9-1 Packaging a non-J2EE Java Application

Description of "Figure 9-1 Packaging a non-J2EE Java Application"

This 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. 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".