Skip Headers

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

Previous | Next |

# Session Bean Applications

For J2EE applications with non-entity 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-3 shows.

Figure 9-3 Packaging a J2EE Application With Non-Entity EJB

Description of "Figure 9-3 Packaging a J2EE Application With Non-Entity EJB"

The component archives with TopLink dependencies include:

- TopLink Domain JAR

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

## EJB JAR

In this type of application, the EJB JAR contains non-entity EJB. Consequently, its `orion-ejb-jar.xml` does not contain `persistence-manager` or `pm-properties` entries. These entries apply only to CMP applications.