Difference between revisions of "EclipseLink/Examples/JPA/Migration/TopLinkEssentials"
(→Using the Package Rename Utility =)
|Line 33:||Line 33:|
== Using the Package Rename Utility
== Using the Package Rename Utility ==
Revision as of 15:58, 23 June 2008
This how-to discusses how a user can migrate to using EclipseLink JPA from TopLink Essentials
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.
- 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