Skip Headers

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

Previous | Next |

# BMP Applications

For J2EE applications that use BMP to persist 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-5 shows.

Figure 9-5 Packaging a J2EE Application With BMP Entity EJB

Description of "Figure 9-5 Packaging a J2EE Application With BMP 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 file specifically services both non-entity and entity EJB. It includes:

- The home and remote, and all implementation code for all mapped beans in the application

- All mapped non-EJB classes from the TopLink Workbench project

- The home and remote, and all implementation code for any session beans included in the application

- Helper classes that contain TopLink amendment methods, and any other classes the application requires

Store the following XML files in the EJB JAR `\meta-inf` directory:

- ejb-jar.xml File

- <J2EE-Container>-ejb-jar.xml File

Because the EJB JAR does not contain entity CMP EJB, its `orion-ejb-jar.xml` must not contain `persistence-manager` or `pm-properties` entries.

For more information, see "Configuring persistence-manager Entries".