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 "Teneo/Hibernate/ModelRelational"

(New page: Teneo can map almost every ecore model to a relational store. The mapping logic is can be overridden and controlled by in-model JPA annotations. The annotations are entered in the model (...)
 
Line 1: Line 1:
 +
 +
== Model Relational Mapping with EJB3/JPA annotations ==
  
 
Teneo can map almost every ecore model to a relational store. The mapping logic is can be overridden and controlled by in-model JPA annotations. The annotations are entered in the model (xsd or ecore) directly or set in a separate XML file:
 
Teneo can map almost every ecore model to a relational store. The mapping logic is can be overridden and controlled by in-model JPA annotations. The annotations are entered in the model (xsd or ecore) directly or set in a separate XML file:

Revision as of 15:20, 21 January 2010

Model Relational Mapping with EJB3/JPA annotations

Teneo can map almost every ecore model to a relational store. The mapping logic is can be overridden and controlled by in-model JPA annotations. The annotations are entered in the model (xsd or ecore) directly or set in a separate XML file:

  • Supported annotations: gives a complete overview of the support for JPA annotations including Hibernate annotation extensions and convenience Teneo extensions.
  • Annotations format: describes in detail how annotations can be specified in the model itself or in a separate XML file. By supporting an external XML it is possible to annotate existing ecore models, so without the need to change them.
  • Association Mapping: describes in detail how associations can be mapped to a relational store, also outlining which annotations and configuration options can be used.

Back to the top