Jump to: navigation, search

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

Line 20: Line 20:
  
 
== Leverage EclipseLink ==
 
== Leverage EclipseLink ==
 +
 +
After completing the conversion to EclipseLink JPA it is also very important to harness the additional features available. The most commonly used features include:
 +
 +
* Caching - ''Ensure you understand and optimize your cache configuration to work with your locking policies and the volatility of your underlying database tables''
 +
** Shared (L2) versus Isoalted (EntityManager/TX)
 +
** Shared type, size, and expiration/invalidation
 +
** Cache coordination (where applicable)
 +
* Query Optimizations - ''Minimize the amount of data loaded and cached for greater performance and optimal cache usage''
 +
** Batch and Joined (multi-level) for graph retrieval
 +
** Cache Usage and Refreshing
 +
** Data Projections for data loading on searches where full entities are not required
 +
** Paged data/entity loading
 +
** Fetch Groups
 +
* Ensure weaving is enabled for change tracking, lazy loading, and fetch groups capabilities

Revision as of 03:19, 3 November 2009

How To Migrate from OpenJPA to EclipseLink JPA

Migrating from OpenJPA to EclipseLink JPA involves a number of standard JPA migration steps plus modification of code to handle extended functionality.

  1. Persistence.XML
    Convert provider and persistence unit properties
  2. Query Hints
    Convert query hint names used in named and dynamic queries
  3. Mappings
    Convert/Fix some non-standard mappings available in OpenJPA
  4. Extended Functionality
    Convert from OpenJPA's extended features
  5. Leverage EclipseLink's Advanced Capabilities

Convert Extended Functionality

OpenJPA does offer some features that go beyond the JPA specification the following sections describe these features and how you migrate to the corresponding functionality in EclipseLink.

  • BigCollection
  • FetchPlan/Group
  • Inheritance Casting
  • Native SQL with POJO results
  • Detached (Serialized) entities & relationships

Leverage EclipseLink

After completing the conversion to EclipseLink JPA it is also very important to harness the additional features available. The most commonly used features include:

  • Caching - Ensure you understand and optimize your cache configuration to work with your locking policies and the volatility of your underlying database tables
    • Shared (L2) versus Isoalted (EntityManager/TX)
    • Shared type, size, and expiration/invalidation
    • Cache coordination (where applicable)
  • Query Optimizations - Minimize the amount of data loaded and cached for greater performance and optimal cache usage
    • Batch and Joined (multi-level) for graph retrieval
    • Cache Usage and Refreshing
    • Data Projections for data loading on searches where full entities are not required
    • Paged data/entity loading
    • Fetch Groups
  • Ensure weaving is enabled for change tracking, lazy loading, and fetch groups capabilities