Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

EclipseLink/Examples/JPA/Employee

< EclipseLink‎ | Examples‎ | JPA
Revision as of 11:01, 2 May 2013 by Douglas.clarke.oracle.com (Talk | contribs) (Try them Out)

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 using GIT and Maven. The basic steps are:

  1. Check out the code
  2. Build and test the projects (mvn test)
  3. Deploy to your favorite web container


You can check the latest versions of all the example projects out of GIT from git.eclipse.org/gitroot/eclipselink/examples.git or browse the source here.

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

Back to the top