Jump to: navigation, search

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

(New page: This how-to discusses how a user can migrate to using EclipseLink JPA from TopLink Essentials * Persistence.xml: custom PU properties * ORM.XML: custom query hints * Annotations: custom q...)
 
Line 1: Line 1:
 
This how-to discusses how a user can migrate to using EclipseLink JPA from TopLink Essentials
 
This how-to discusses how a user can migrate to using EclipseLink JPA from TopLink Essentials
  
* Persistence.xml: custom PU properties
+
== Persistence.xml ==
* ORM.XML: custom query hints
+
 
* Annotations: custom query hints
+
=== Persistence Provider ===
 +
 
 +
=== Properties ===
 +
 
 +
When migrating the Persistence.xml the primary change in the persistence unit properties is converting from using "toplink.*" to "eclipseLink.*"
 +
 
 +
== ORM.XML ==
 +
 
 +
TopLink Essentials uses the JPA 1.0 defined orm.xml schema and thus is compatible with EclipseLink. The only content changes that should be made is conversion of any query hints used in the configuration.
 +
 
 +
=== Query Hints ===
 +
 
 +
== Annotations ==
 +
 
 +
=== Query Hints ===
 +
 
 +
== Java API ==
 +
 
 +
=== Query Hints ===
 +
 
 
* Java code: customer PU properties and query hints
 
* Java code: customer PU properties and query hints
 
** Use of EclipseLink native API where TLE native API was used
 
** Use of EclipseLink native API where TLE native API was used
Line 9: Line 28:
 
* Side-effects of the migration
 
* Side-effects of the migration
 
** Change from default access type when using ORM.XML
 
** Change from default access type when using ORM.XML
 +
 +
=== Custom Mapping Definitions ===
 +
 +
 +
 +
== Using the Package Rename Utility ===

Revision as of 21:22, 28 March 2008

This how-to discusses how a user can migrate to using EclipseLink JPA from TopLink Essentials

Persistence.xml

Persistence Provider

Properties

When migrating the Persistence.xml the primary change in the persistence unit properties is converting from using "toplink.*" to "eclipseLink.*"

ORM.XML

TopLink Essentials uses the JPA 1.0 defined orm.xml schema and thus is compatible with EclipseLink. The only content changes that should be made is conversion of any query hints used in the configuration.

Query Hints

Annotations

Query Hints

Java API

Query Hints

  • Java code: customer PU properties and query hints
    • Use of EclipseLink native API where TLE native API was used
  • Side-effects of the migration
    • Change from default access type when using ORM.XML

Custom Mapping Definitions

Using the Package Rename Utility =