Jump to: navigation, search


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


Persistence Provider


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


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


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