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 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.
Try them Out
To try out these examples using GIT, Maven, and the Eclipse Java EE IDE. These example projects can be adapted for other development environments.
Check out the code
You can check the latest versions of all the example projects out of GIT from:
- Eclipse.org: git.eclipse.org/gitroot/eclipselink/examples.git or browse the source here.
- GitHub: 
Build and Test
The model project comes with test cases that validate the JPA model and its services function correctly. It is configured to run on embedded derby by default so generally running 'mvn test' in the model project will run the examples and test cases and let you know that everything is working correctly.
Setup your Container
- Requires a data source named 'java:global/employeeDS' which the user is required to set up.
- Convenience scripts to do this are provided under employee.model\src\config\weblogic.
- Usage example: createDataSource.cmd C:\Oracle\Middleware\wlserver_12.1
Deploy and Try
Once the application is successfully deployed you can navigate to the homepage:
The first thing you'll want to do at this point is set up your database tables. You can also populate some test data as well. To do this from the Admin page.
- add intro screen shot
- highlight key operations
- Admin to reset database and populate
- Search and pagination options
(very basic details only)
Understanding the Example
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.
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.gendermapped 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.