Skip to main content

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.

Jump to: navigation, search

Texo/Code Generation Details

< Texo
Revision as of 04:59, 14 May 2010 by Unnamed Poltroon (Talk) (What is an Annotations Model)

Introduction

The Texo code generation is controlled by annotations on the model. These annotations determine the class names, names of methods and java package names. When Teneo generates code it will automatically create these annotations (in-memory) for each model element (EClass, EStructuralFeature). However, it is also possible to define these annotations in a so-called annotations model. This gives you the possibility to override the choices made by the Texo code generator. Texo will use these manual annotations and add its own annotations to have a complete annotated model.

This document describes how the annotations model works and how you can define the annotations model.

What is an Annotations Model

An annotations model is very similar to the ecore model or xsd. An annotations model has references to the original ecore model and adds extra information to store directives for code generation. The screenshot below shows an example of an annotations model.


Org.eclipse.emf.texo.annotations.model.png


The above screenshot

Creating and Editing an Annotations Model

The first step in creating an annotations model

Code Generation Properties (annotations)

This section gives a detailed description of the properties/features in the annotations model used for code generation.

EPackage Model Gen Features

EClass Model Gen Features

EReference Model Gen Features

EDataType Model Gen Features

EEnum Model Gen Features

Back to the top