Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/JPA/Migration/OracleTopLinkNative"

m
 
(20 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Under Construction ==
+
'''[[Image:Elug_draft_icon.png|Warning]] This page is obsolete. Please see "Migrating from Native TopLink to EclipseLink" in the ''[http://www.eclipse.org/eclipselink/documentation/2.4/solutions/migrnativetoplink.htm EclipseLink Solutions Guide]'' for current information.'''
 
+
==Migrating from Oracle TopLink to EclipseLink==
+
 
+
This article will give an overview of how to migrate an Oracle TopLink project to EclipseLink
+
 
+
===Deprecated Oracle TopLink API===
+
 
+
API that has been deprecated in Oracle TopLink will be removed from EclispeLink. If your code makes use of any deprecated TopLink API, you will have to update it to use the API recommended in the deprecation comment.
+
 
+
===Rename Packages===
+
 
+
The base package has been renamed from "oracle.toplink" to "org.eclipse.persistence". Some lower level packages have also been refactored. To cope with this issue and package rename tool is included in the intstall.  This package renamed replaces package and class references with the updated ones.  You should run the tool on your source code, project xml, persistence.xml and sessions.xml
+
 
+
====Running the Package Renamer====
+
 
+
===Dealing with XML Configuration files===
+
 
+
====Sessions XML====
+
 
+
====Deployment XML====
+
 
+
====Persistence XML====
+
 
+
====ORM XML====
+

Latest revision as of 12:51, 30 January 2013

Warning This page is obsolete. Please see "Migrating from Native TopLink to EclipseLink" in the EclipseLink Solutions Guide for current information.

Back to the top