Difference between revisions of "EclipseLink/Examples/JPA/Employee"

From Eclipsepedia

Jump to: navigation, search
(GIT)
(EclipseLink JPA Employee Examples)
Line 2: Line 2:
  
 
This set of examples uses a common employee domain model and relational schema with various configuration approaches.
 
This set of examples uses a common employee domain model and relational schema with various configuration approaches.
* '''Annotations''': JPA using standard and extended annotations
+
* '''Model''': JPA using standard and extended annotations along with eclipselink-orm.xml mapping file.
* '''XML''': JPA using extended eclipselink-orm.xml mapping file
+
* '''Model No SQL''': JPA using standard and extended annotations along with eclipselink-orm.xml mapping file on a NoSql platform.
 +
* '''Model Web''': JPA using standard and extended annotations along with eclipselink-orm.xml mapping file with a web interface.
 +
* '''Model Web JS''': JPA using standard and extended annotations along with eclipselink-orm.xml mapping file with a web interface.
 
* '''Dynamic''': Dynamic persistence (no Java classes) mapped using API and eclipselink-orm.xml
 
* '''Dynamic''': Dynamic persistence (no Java classes) mapped using API and eclipselink-orm.xml
  

Revision as of 10:29, 8 April 2013

Contents

EclipseLink JPA Employee Examples

This set of examples uses a common employee domain model and relational schema with various configuration approaches.

  • Model: JPA using standard and extended annotations along with eclipselink-orm.xml mapping file.
  • Model No SQL: JPA using standard and extended annotations along with eclipselink-orm.xml mapping file on a NoSql platform.
  • Model Web: JPA using standard and extended annotations along with eclipselink-orm.xml mapping file with a web interface.
  • Model Web JS: JPA using standard and extended annotations along with eclipselink-orm.xml mapping file with a web interface.
  • Dynamic: Dynamic persistence (no Java classes) mapped using API and eclipselink-orm.xml

Try them Out

To try out these examples you can download from the project's GIT repository or you can download the packaged projects.

GIT

You can check the latest versions of all the example projects out of GIT from git.eclipse.org:

Download

Understanding the Examples

Employee Model

The employee model has existed in TopLink and EclipseLink since the mid 90's. The model has evolved a little over the years based on enhancements made available in the mappings.

EclipseLink Example Employee model.png

JPA 2.0 and Extended Features

When updated for EclipseLink 2.1 several JPA 2.0 features were introduced to the model and its mappings. These include:

  • PhoneNumber now mapped using derived identifiers so its primary key of EMP_ID and PTYPE are mapped with PhoneNumber.owner and PhoneNumber.type. The previous redundant mapping of PhoneNumber.id has been removed.

While the majority of the Employee examples use pure JPA mappings several extensions offered by EclipseLink are highlgted including:

  • Employee.gender mapped to the enum Gender using a converter to store a single char code in the database instead of the full enum's name or oridinal position.

Configuration Options

  • Annotations
  • ORM XML
    • EclipseLink ORM
    • JPA ORM + EclipseLink ORM