<persistence-manager>

The <persistence-manager> section provides additional deployment information for the TopLink persistence manager for EJB 2.1 applications only. For EJB 3.0 applications, OC4J always uses the TopLink entity manager.

The <persistence-manager> section contains the following structure:

<persistence-manager name=... class=... descriptor=... >
  <pm-properties>
    <session-name>...</session-name>
    <project-class>...</project-class>
    <db-platform-class>...</db-platform-class>
    <default-mapping db-table-gen=... >...</default-mapping>
    <remote-relationships>...</remote-relationships>
    <cache-synchronization mode=... >...</cache-synchronization>
    <customization-class>...</customization-class>
  </pm-properties>
</persistence-manager>

Multiple definitions of the <persistence-manager> element are not valid. If OC4J detects multiple definitions of the <persistence-manager> element at parse time, OC4J logs a warning message. In this case, OC4J uses only the first entry and ignores any subsequent entries.

If you want to explicitly specify the persistence manager, use the <persistence-manager> element name attribute. The following are valid values:

• toplink: selects the TopLink persistence manager (default).

• orion: selects the deprecated Orion persistence manager.

If you are using the TopLink persistence manager and you name your TopLink deployment descriptor something other than toplink-ejb-jar.xml (see "What is the toplink-ejb-jar.xml File?"), specify the name using the <persistence-manager> element descriptor attribute.

The <pm-properites> element applies only to the TopLink persistence manager.

For more information, see the following:

• "Understanding EJB Persistence Services"

• "Customizing the JPA Persistence Provider"

• "Customizing the TopLink EJB 2.1 Persistence Manager"

• "Configuring pm-properties" in the Oracle TopLink Developer’s Guide