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.
Texo/Texo and EMF
Contents
Introduction
Texo usage of EMF components
Texo uses the following EMF components in its overall solution:
- Runtime model (EClass, EStructuralFeature, etc.)
- XSD to Ecore
- XML serialization
Texo does not make use of the EMF code generation framework. Texo implements its own code generation of entities and pojos.
Differences between EMF and Texo
Texo is targeted at server-side technology (such as web-server and web-service environments). EMF code generation is targeted for usage in Eclipse RCP products. This different target environments mean that the generated code and functionality. Texo does not (and will not) support or generate code for the following cases:
- EMF list implementations such as bidirectional or containment lists
- eContainer or containment associations (they are used in the XML serialization supported by Texo but not explicitly expressed in the java code as now in EMF)
- Notifications and notifiers
- Adapters
- Generation of EMF Edit/Editor or other RCP related constructs
This type of functionality is of less use in server environments.
EMF-functionality to be implemented in Texo
Although some EMF functionality is explicitly not supported there are is also EMF functionality which is currently not supported but which is planned to be supported:
- The unsettable concept of EMF: is used in XML serialization to determine if an element is present in the XML or not
- [Other topics to be added]
EMF to Texo mapping
Texo has similarities with EMF and some EMF concepts are re-implemented in Texo, sometimes in a different way. Texo will support full XML Schema support and XML (de-)serialisation.
There is one specific implementation detail which is supported