Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EMF/Teneo 1.0.4/EclipseLink Support"

< EMF
Line 10: Line 10:
 
== Accessing EMF Models in Databases using the EclipseLink Resource ==
 
== Accessing EMF Models in Databases using the EclipseLink Resource ==
  
Teneo/EclipseLink provides a full implementation of EMF's Resource interface (org.eclipse.emf.ecore.resource.Resource). It enables applications to load and save EMF models from or to relational databases and to manage their lifecycle directly through EMF's built-in persistence API, i.e. the ResourceSet interface (org.eclipse.emf.ecore.resource.ResourceSet).  
+
Teneo/EclipseLink provides a full implementation of EMF's Resource interface named EclipseLinkResourceImpl. It enables applications to load and save EMF models from or to relational databases and to manage their lifecycle directly through EMF's built-in persistence API, i.e. the ResourceSet interface. EclipseLinkResourceImpl represents an almost complete abstraction from JPA mappings and EclipseLink APIs and makes accessing models in databases, from an EMF point of view, as natural as loading or saving models from files.
 +
 
 +
EclipseLinkResourceImpl
  
 
== Building Model-based Rich Client Applications on top of Teneo and EclipseLink ==
 
== Building Model-based Rich Client Applications on top of Teneo and EclipseLink ==

Revision as of 01:12, 16 March 2009

Teneo 1.0.4 provides support for EclipseLink. The following sections explain the principal features it includes and give advice how they can be used for building model-based applications on top of relational databases.

Creating EclipseLink/JPA Mappings for EMF models

Three possibilities:

  • Model-driven
  • Meet-in-the-middle
  • Schema-driven

Accessing EMF Models in Databases using the EclipseLink Resource

Teneo/EclipseLink provides a full implementation of EMF's Resource interface named EclipseLinkResourceImpl. It enables applications to load and save EMF models from or to relational databases and to manage their lifecycle directly through EMF's built-in persistence API, i.e. the ResourceSet interface. EclipseLinkResourceImpl represents an almost complete abstraction from JPA mappings and EclipseLink APIs and makes accessing models in databases, from an EMF point of view, as natural as loading or saving models from files.

EclipseLinkResourceImpl

Building Model-based Rich Client Applications on top of Teneo and EclipseLink

Back to the top