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"
(→Continuous Build) |
(→CVS, Support, Commit Mailing List and FAQ) |
||
| Line 23: | Line 23: | ||
* EMF 2.6 (Eclipse 3.6): for this EMF version the Teneo builds numbered 1.2.0 should be used. | * EMF 2.6 (Eclipse 3.6): for this EMF version the Teneo builds numbered 1.2.0 should be used. | ||
| − | == | + | == GIT, Support, Commit Mailing List and FAQ == |
| − | The Teneo source code | + | The Teneo source code is stored in git in this location: |
| − | + | {{Git|teneo|org.eclipse.emf.teneo.git}} | |
| − | + | ||
| − | + | ||
If you encounter issues, check the [[Teneo/Hibernate/FAQ|FAQ]] page. | If you encounter issues, check the [[Teneo/Hibernate/FAQ|FAQ]] page. | ||
Revision as of 16:45, 1 November 2011
Contents
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 for Model Relational mapping within the CDO Hibernate Store.
Features
- Powerful Tool Combination: Teneo integrates EMF with existing persistency solutions, combining strong model-driven code generation functionality with 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 server-oriented environments with business logic running on the server. 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.4 should be used.
- EMF 2.5 (Eclipse 3.5): for this EMF version the Teneo builds numbered 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.
GIT, Support, Commit Mailing List and FAQ
The Teneo source code is stored in git in this location: org.eclipse.emf.teneo.git (browse, stats, fork on OrionHub)
If you encounter issues, check the FAQ page.
Support for Teneo is given on the EMF newsgroup. For accessing the news group through a browser visit this page. To read newsgroups using a client application, install Pan Newsreader (pan Debian/Ubuntu package) or KNode (knode Debian/Ubuntu package).
To subscribe to the commit mailing list, visit this page: https://dev.eclipse.org/mailman/listinfo/teneo-commit
Continuous Build
Teneo is build using Buckminster and Hudson in a continuous build system.
- Teneo nightly build job
- Detailed description on Teneo's build setup
Update site containing the latest successful nightly builds: https://hudson.eclipse.org/hudson/job/emf-teneo-nightly/lastSuccessfulBuild/artifact/build/result/p2site/