|
Oracle® Application Server TopLink Getting Started Guide
10g Release 2 (10.1.2) Part No. B15902-01 |
|
 Previous |
 Next |
|
Oracle® Application Server TopLink Getting Started Guide
10g Release 2 (10.1.2) Part No. B15902-01 |
|
|
Previous |
Next |
For users that have not previously migrated to Release 2 (9.0.3), this chapter describes how to migrate existing 2.x, 3.x and 4.x projects to Oracle Application Server TopLink 10g Release 2 (10.1.2). This chapter includes the following sections:
Use the following procedures to upgrade your project from a previous version of the OracleAS TopLink Mapping Workbench.
From Release 2 (9.0.3)
Open and save the project with 10g Release 2 (10.1.2).
|
Note: In Release 2 (9.0.4), enhancements to the OracleAS TopLink Mapping Workbench included a significant reduction of XML files. If you are using the OracleAS TopLink Mapping Workbench with a source control management (SCM) system in Release 2 (9.0.3) projects, many files in the SCM will no longer be valid in 10g Release 2 (9.0.4.x) /10g Release 2 (10.1.2). |
From Version 4.x
Use the "Package Rename" procedures and open the project with 10g Release 2 (10.1.2).
From Version 3.6
Use the "Package Rename" procedures and open the project with 10g Release 2 (10.1.2).
From Versions 2.x, 3.0 or 3.5
If you are migrating an OracleAS TopLink Mapping Workbench project from a version prior to version 3.6, contact Oracle Support Services support for assistance at OracleMetaLink.
|
Note: The Default Null value for object type mappings was expanded (starting with version 4.6) to differentiate between default and null values. If your 3.6 project contains object type mappings ensure that the default and null values are set properly on the mapping's General tab. For more information, see the Oracle Application Server TopLink Mapping Workbench User's Guide. |
|
Note: If you receiveClassNotFound exceptions after you migrate a project, ensure the JDBC_CLASSPATH variable does not include any Java classes for your persistent business objects. Paths for persistent business objects are set within an OracleAS TopLink Mapping Workbench project. For more information on how to set up a path for a project, see the Oracle Application Server TopLink Mapping Workbench User's Guide.
Also check your project classes for any references to legacy OracleAS TopLink classes. |
Beginning with Release 2 (9.0.3), the base package for the entire structure became oracle.toplink. To upgrade existing application source code which refers to OracleAS TopLink API packages and existing OracleAS TopLink Mapping Workbench projects previous to Release 2 (9.0.3), you must use the Package Rename tool.
Use the Package Rename tool on your:
Source code
Configuration files
OracleAS TopLink Mapping Workbench project files that contain references to pre-Release 2 (9.0.3) API packages
The Package Rename tool works on plain text files and must not be used with binary files such as jar files.
Use this procedure to upgrade your existing pre-Release 2 (9.0.3) application source code and OracleAS TopLink Mapping Workbench projects to version 10g Release 2 (10.1.2).
At the command prompt, execute the packageRename.cmd/sh program located in the ORACLE_HOME/toplink/bin directory. You need to specify three parameters on the command line:
the complete directory path that contains the Java source code of your existing project
the complete directory path that will contain the upgraded 10g Release 2 (10.1.2) project
the name of a log file. If no file is specified, the logging messages will print to standard output.
Press Enter and the Package Rename tool will upgrade your project. The Package Rename tool requires approximately 15 minutes for a 1MB file. Larger files may require additional time.
Repeat this procedure for your:
Source code
Configuration files
OracleAS TopLink Mapping Workbench project files (*.mwp, *.xml)
Table 3-1, Table 3-2, Table 3-3 and Table 3-4 identify the name changes between version 4.x and 10g Release 2 (10.1.2).
Table 3-1 New Package Names
| Version 4.x | Release 2 (9.0.3) | 10g Release 2 (9.0.4) and 10g Release 2 (10.1.2) |
|---|---|---|
com.webgain.integrator
|
oracle.toplink
|
oracle.toplink
|
com.webgain.workbench
|
oracle.toplink.workbench
|
oracle.toplink.workbench
|
com.webgain.openapi. foundation
|
oracle.toplink.uitools
|
oracle.toplink.uitools
|
Table 3-2 New Class Names
| Version 4.x | Release 2 (9.0.3) | 10g Release 2 (9.0.4) and 10g Release 2 (10.1.2) |
|---|---|---|
WDIException.java
|
TopLinkException.java
|
TopLinkException.java
|
Table 3-3 New JAR/WAR Names
| Version 4.x | Release 2 (9.0.3) | 10g Release 2 (9.0.4) and 10g Release 2 (10.1.2) |
|---|---|---|
wdiall.jar
|
toplink.jar
|
toplink.jar
|
wdi.jar
|
tl_core.jar
|
not applicable |
wdisdk.jar
|
tl_sdk.jar
|
not applicable |
wdisdkxerces.jar
|
tl_sdkx.jar
|
not applicable |
wditools.jar
|
tl_tools.jar
|
not applicable |
wdix.jar
|
tl_x.jar
|
not applicable |
wdiwasx.jar
|
tl_wasx.jar
|
not applicable |
wdiwlsx.jar
|
tl_wlsx.jar
|
not applicable |
workbench.jar
|
workbench.jar
|
toplinkmw.jar
|
TopLinkWebClient.war
|
tl_webclient.war
|
toplinkwc.war
|
wdidemo.jar
|
tl_demo.jar
|
not applicable |
wdidemoui.jar
|
tl_tour.jar
|
not applicable |
Table 3-4 New XML/DTD Files
| Version 4.x | Release 2 (9.0.3) | 10g Release 2 (9.0.4) and 10g Release 2 (10.1.2) |
|---|---|---|
wdi-ejb-jar.xml
|
toplink-ejb-jar.xml
|
toplink-ejb-jar.xml
|
wdi-was-ejb-jar_45.dtd
|
toplink-was-ejb-jar_903.dtd
|
toplink-was-ejb-jar_904.dtd
|
wdi-wls-ejb-jar_40.dtd
|
toplink-wls-ejb-jar_903.dtd
|
toplink-wls-ejb-jar_904.dtd
|
OracleAS TopLink 10g Release 2 (10.1.2) is backward compatible with previous releases however, you must update the DOCTYPE headers for the Sessions XML files to read as follows:
Table 3-5 Sessions.xml
| DocType | DTD Used From the Classpath |
|---|---|
| "-//Oracle Corp.//DTD TopLink for JAVA 4.0//EN" | sessions_4_0.dtd |
| "-//Oracle Corp.//DTD TopLink for JAVA 4.5//EN" | sessions_4_5.dtd |
| "-//Oracle Corp.//DTD TopLink Sessions 9.0.4//EN" | sessions_9_0_4.dtd |
