Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Teneo"
| Line 8: | Line 8: | ||
* '''Flexible''': Teneo automatically maps models to relational database schema. The mapping can be overridden and extended with JPA annotations in the model itself or in a separate xml file. For more information visit the links below. | * '''Flexible''': Teneo automatically maps models to relational database schema. The mapping can be overridden and extended with JPA annotations in the model itself or in a separate xml file. For more information visit the links below. | ||
| − | * '''Extensive''': Teneo supports persistence of virtually every ecore model out-of-the-box without | + | * '''Extensive''': Teneo supports persistence of virtually every ecore model out-of-the-box without additional manual mapping work. |
* '''Server-Side-Solutions''': Teneo is primarily for (web-)server environments. Especially web-service solutions can benefit from advanced EMF XML (de-)serialization support combined with automatic Model-Relational mapping and powerfull runtime persistence using standards compliant ORM solutions. | * '''Server-Side-Solutions''': Teneo is primarily for (web-)server environments. Especially web-service solutions can benefit from advanced EMF XML (de-)serialization support combined with automatic Model-Relational mapping and powerfull runtime persistence using standards compliant ORM solutions. | ||
Revision as of 10:22, 21 January 2010
Teneo is a Model-Relational mapping and runtime solution for the Eclipse Modeling Framework (EMF).
Teneo benefits:
- Powerfull: Teneo integrates EMF with existing persistency solutions, combines the power of a code generation framework like EMF and the power of storage, caching and querying of sophisticated object-relational mapping and persistency software.
- Flexible: Teneo automatically maps models to relational database schema. The mapping can be overridden and extended with JPA annotations in the model itself or in a separate xml file. For more information visit the links below.
- Extensive: Teneo supports persistence of virtually every ecore model out-of-the-box without additional manual mapping work.
- Server-Side-Solutions: Teneo is primarily for (web-)server environments. Especially web-service solutions can benefit from advanced EMF XML (de-)serialization support combined with automatic Model-Relational mapping and powerfull runtime persistence using standards compliant ORM solutions.
Teneo integrates EMF with both Hibernate and EclipseLink. For detailed information, manuals and tutorials for each solution visit the ORM specific page:
- Hibernate: The EMF - Hibernate integration supports persisting of basic EObjects, ELists with 1:n, n:m, one-way, two-way and contained relations. EMF Objects can be retrieved using HQL queries. For more information see here
- EclipseLink: The EMF - EclipseLink integration is a fully JPA compliant solution using the EclipseLink orm tool. For more information see here
Teneo supports the three current EMF versions:
- EMF 2.4 (Eclipse 3.4): for this EMF version the Teneo release numbered 1.0.* (current maintenance build is 1.0.4) should be used.
- EMF 2.5 (Eclipse 3.5): for this EMF version the Teneo builds numbered 1.1.0/1.1.1/1.1.2 should be used.
- EMF 2.6 (Eclipse 3.6): for this EMF version the Teneo builds numbered 1.2.0 should be used.