Skip Headers

# EJB JAR

Previous

Next

In this type of application, the EJB JAR file specifically service both non-entity and entity EJB. It includes the following:

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

  For example, an instance of `oracle.toplink.ejb.cmp.DeploymentCustomization` (for more information, see `customization-class` in Table: orion-ejb-jar.xml File persistence-manager Subentries for pm-properties in "Configuring persistence-manager Entries").

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

- ejb-jar.xml File

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

- toplink-ejb-jar.xml File

Note: If you do not use XML files for deployment, include your compiled `oracle.toplink.sessions.Project` file at the root of the EJB JAR (not in the `\meta-inf` directory).

Because the EJB JAR contains both session and entity beans, if you are using OC4J or BEA WebLogic (WLS), the `<J2EE-Container>-ejb-jar.xml` file must contain `persistence-manager` and `pm-properties` entries. For more information, see "Configuring persistence-manager Entries".

You must persist all of the entity beans to the same data source. For a CMP application, TopLink does not support the session broker functionality (see "Session Broker and Client Sessions").