Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Teneo"

Line 2: Line 2:
  
  
'''Target Environment''': Teneo with EMF is particularly well-suited for use in ''server oriented model-driven web-service and web application environments''.  
+
'''Web-service/Web application''': Teneo with EMF is particularly well-suited for use in ''server oriented model-driven web-service and web application environments''.  
  
  
'''CDO''': in addition Teneo is being used for Model Relational mapping within the [[CDO_Hibernate_Store|CDO Hibernate Store]] which is part of the [[CDO|CDO]] project.
+
'''RCP''': if you want to develop a RCP with less emphasys on custom server side logic consider using [[CDO|CDO]]. Teneo is used used for Model Relational mapping within the [[CDO_Hibernate_Store|CDO Hibernate Store]].
  
  

Revision as of 06:27, 23 January 2010

EMF & ORM: Teneo is a Model-Relational mapping and runtime database persistence solution for the Eclipse Modeling Framework (EMF). Teneo integrates EMF with both Hibernate and EclipseLink.


Web-service/Web application: Teneo with EMF is particularly well-suited for use in server oriented model-driven web-service and web application environments.


RCP: if you want to develop a RCP with less emphasys on custom server side logic consider using CDO. Teneo is used used for Model Relational mapping within the CDO Hibernate Store.


Teneo benefits:

  • Powerful Tool Combination: Teneo integrates EMF with existing persistency solutions, combining code generation framework like EMF and the power of storage, caching and querying of sophisticated object-relational mapping and persistency software.
  • Flexible Approach: Teneo automatically maps models to relational database schema. The mapping can be fully controlled, overridden and extended with JPA annotations in the model itself or in a separate xml file.
  • Extensive Coverage: 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 the EMF XML (de-) serialization support combined with automatic Model-Relational mapping and runtime database persistence.


Documentation: For detailed information, manuals and tutorials for each solution visit the ORM specific part of the site:

  • 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


Versions: 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.

Back to the top