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.
Teneo/APIPolicy
Teneo consists of 2 main parts:
- a mapping layer
- a runtime layer
At runtime Teneo works behind the scenes and has a very limited runtime api for initialization. This api is kept stable over the past releases.
The mapping layer generates mappings to relational databases on the basis of domain models (ecore). The mapping stability is tested by checking that changes/fixes to Teneo do not result in changes in the generated mapping. In case mapping output changes always a configuration option is added to support the previous mapping approach. Teneo has 40+ configuration options, see here.
The direct java api is very limited and it has been stable for many years. There are no plans to introduce backward compatibility in this api neither are there plans to introduce larger changes or additions in this api. The current api will be maintained until the end-of-live of Teneo.