Teneo--Integrating EMF & EclipseLink for Model-Driven Development with Persistence
7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18
Shaun Smith
Martin Taal
Teneo’s EclipseLink/EMF integration addresses the problem of persisting EMF models in relational databases using the standard Java Persistence API (JPA). It integrates with existing EMF Runtime through its implementation of the EMF resource model for EclipseLink JPA.
Teneo supports a fully top-down model driven approach that generates EMF classes, default JPA mappings for those classes, and the database schema required to persist those classes from a single Ecore model. Ecore annotations can be used to customize the generated JPA mappings and relational schema.
Teneo also supports the meet-in-the-middle approach of mapping EMF classes to an existing relational schema. This enables the construction of model driven applications on top of existing or legacy databases. Teneo can be combined with the Dali JPA Tools for meet-in-the-middle development with Dali providing intelligent mapping assistance and validation against the target relational schema.
This session will combine slides and demos to illustrate both the design time and runtime functionality of Teneo and EclipseLink.
The following topics will be addressed in detail:
- Top-down/Model-driven development
- Meet-in-the-middle mapping
- Ecore JPA Annotations
- Idioms for mapping EMF with JPA
- Orphan Management
- EclipseLink OSGI JPA
- Performance
- A comparison of Teneo/EclipseLink with CDO
Shaun Smith is a product manager for Oracle TopLink and an active member of the Eclipse community. He's Ecosystem Development Lead for the Eclipse Persistence Services Project (EclipseLink), a committer on the Eclipse EMFT Teneo,and Dali Java Persistence Tools projects.