TopLink Persistence Manager Support

Table A-1 summarizes which orion-ejb-jar.xml options are applicable to TopLink CMP. For example:

To configure <entity-deployment> attribute call-timeout, you must use the corresponding TopLink persistence manager API. If you set the call-timeout attriubte in the orion-ejb-jar.xml file, OC4J will ignore it.
To configure <entity-deployment> attribute clustering-schema, you must use the orion-ejb-jar.xml file; there is no corresponding TopLink persistence manager API.

Table A-1 OC4J orion-ejb-jar.xml Features and TopLink

orion-ejb-jar.xml Feature	Configurable in orion-ejb-jar.xml	Configurable in toplink-ejb-jar.xml
`<entity-deployment>`
`clustering-schema`
`copy-by-value`
`data-source`
`location`
`max-instances`
`min-instances`
`max-tx-retries`
`disable-wrapper-cache`
`name`
`pool-cache-timeout`
`wrapper`
`local-wrapper`
`call-timeout`
`exclusive-write-access`
`true`
`false`
`do-select-before-insert`
`true`
`false`
`isolation`
`locking-mode`
`pessimistic`
`optimistic`
read-only
`old_pessimistic`
`update-changed-fields-only`
`true`
`false`
`table`
`force-update`
true
false
`data-synchronization-option`
ejbCreate
ejbPostCreate
`batch-size`
Any value greater than 1
`<ior-security-config>`
`<env-entry-mapping>`
`<resource-ref-mapping>`
`<resource-env-ref-mapping>`
`<primkey-mapping>`
`<cmp-field-mapping>`
`one-to-one-join`
inner
outer^Foot 1
shared
`<finder-method>`
`<persistence-type>`^Foot 2

^Footnote 1TopLink supports both outer and inner joins at run time.You can manually configure EJB descriptors with these options. For more information, "Understanding TopLink Queries" in the Oracle TopLink Developer's Guide.

^Footnote 2The persistence-type attribute's table column size, if present, is discarded. For more information, "Migrating OC4J Orion Persistence to OC4J TopLink Persistence" in the Oracle TopLink Developer's Guide.

For EJB 3.0 applications, you can access TopLink persistence manager API by augmenting orion-ejb-jar.xml configuration with TopLink-specific deployment descriptor files ejb3-toplink-sessions.xml and toplink-ejb-jar.xml. For more information, see "Customizing the TopLink Entity Manager".

For EJB 2.1 applications, you can access TopLink persistence manager API using orion-ejb-jar.xml element pm-properties. For more information, see "Customizing the TopLink Persistence Manager".

Note:

When using OC4J with TopLink, use TopLink Workbench to modify the toplink-ejb-jar.xml file. Refer to the Oracle TopLink Developer's Guide for complete information on migrating information from the orion-ejb-jar.xml file.

The ejb3-toplink-sessions.xml and toplink-ejb-jar.xml file conform to the XML schema documents located at <OC4J_HOME>\toplink\config\xsds.