Skip to main content
Jump to: navigation, search

Difference between revisions of "Texo/ORM JPA Annotations Details"

(New page: __TOC__ == Texo Mapping Decisions == Texo makes the following mapping decisions when generating an orm.xml: * as a default all access is set at FIELD (this in contrast to the JPA default...)
 
Line 1: Line 1:
 
__TOC__
 
__TOC__
 +
 +
== Introduction ==
 +
 +
The Texo ORM generation can be controlled completely through an [[Texo/Code_Generation_Details#What_is_an_Annotations_Model|annotations model]]. The ORM/JPA model annotations make it possible to override/set all orm 2.0 annotations at model level. You only need to annotate the parts of the model which need extra attention. Texo will automatically add any missing annotations to get to a fully annotated model (while maintaining the manual settings).
 +
 +
 +
 +
[[Image:org.eclipse.emf.texo.generate.orm.png|center]]
 +
  
 
== Texo Mapping Decisions ==
 
== Texo Mapping Decisions ==

Revision as of 17:05, 17 May 2010

Introduction

The Texo ORM generation can be controlled completely through an annotations model. The ORM/JPA model annotations make it possible to override/set all orm 2.0 annotations at model level. You only need to annotate the parts of the model which need extra attention. Texo will automatically add any missing annotations to get to a fully annotated model (while maintaining the manual settings).


Org.eclipse.emf.texo.generate.orm.png


Texo Mapping Decisions

Texo makes the following mapping decisions when generating an orm.xml:

  • as a default all access is set at FIELD (this in contrast to the JPA default which is PROPERTY), only interfaces will use the PROPERTY access type.
  • join tables are named as: entityname_efeaturename. This in contrast to the JPA default which specifies that a join table should be the concatenation of the names of the 2 tables which are joined. Texo uses a different approach as it provides a more robust naming without collisions.
  • Texo will automatically manage which side is the owner in a bi-directional association.
  • Texo chooses the entity name (is the same as the EClass name).

Future extensions

  • Support the Map type
  • Generate more database schema constructs in the orm.xml (column names for example).
  • Make the database artifact/entity naming logic configurable

Back to the top