Oracle® Containers for J2EE Enterprise JavaBeans Developer's Guide 10g (10.1.3.1.0) Part Number B28221-02 |
|
|
View PDF |
The toplink-ejb-jar.xml
file is applicable only if you are using the TopLink JPA preview persistence provider.
Note:
By default, OC4J uses the TopLink Essentials JPA persistence provider. In this case, you can configure TopLink descriptor-level options (including mappings) using TopLink JPA extensions ("Accessing TopLink API at Run Time With TopLink Essentials JPA Persistence").This section describes the following:
For more information, see the following:
"OC4J and the toplink-ejb-jar.xml File" in the Oracle TopLink Developer's Guide
For EJB 2.1 projects only, when you migrate an Orion CMP application to TopLink persistence (see "Migrating to the TopLink EJB 2.1 Persistence Manager"), the TopLink migration tool automatically creates a toplink-ejb-jar.xml
file for you.After generation, you can use the TopLink Mapping Workbench to customize and reexport (see "Understanding the TopLink Workbench" in the Oracle TopLink Developer's Guide).
For EJB 3.0 projects, if the only JDK 1.5 language extension that your entity classes use are annotations, you can use the TopLink Workbench to create and configure a toplink-ejb-jar.xml
file. Oracle recommends using the TopLink Workbench to create and configure this file.
For EJB 2.1 projects, you use the TopLink Workbench to configure persistence properties in the toplink-ejb-jar.xml
file. When you migrate an Orion CMP application to TopLink persistence (see "Migrating to the TopLink EJB 2.1 Persistence Manager"), the TopLink migration tool automatically creates a TopLink Workbench project for you. You can use the TopLink Workbench project to create a toplink-ejb-jar.xml
file.
For more information, see the following:
"Understanding the TopLink Workbench" in the Oracle TopLink Developer's Guide
"Creating project.xml with TopLink Workbench" in the Oracle TopLink Developer's Guide.