The generated orm.xml refers to the classes/java members/types as generated by Texo code generation (so taking into account any model generate annotations you have specified).

When generating the orm.xml Texo tries to make use of the default capabilities of the ORM layer. This means that only the necessary decisions (for example naming) are made by Texo. You can override/extend the generated orm.xml by specifying ORM annotations on the model. This is done in the same way as with the code generation annotations. For more information on annotations models, see Texo Code Generation details.

Generating JPA annotated model code

Right click on an ecore/xsd file and then in the Texo submenu click 'Generate JPA Annotated Model Code'

The JPA annotations will be present in the source code.

Generating an orm.xml

It is quite easy to generate an orm.xml from a model: right-click on the ecore model and select Texo > Generate

The orm.xml will be created in the same folder as the ecore file which was selected. Any existing orm.xml in that same folder will be overwritten.

This pages shows how you can create an orm.xml directly from an ecore model. Often it makes sense to tweak or change the ORM mapping. This can be done using annotations on the model, or in other words an ORM annotation model, see here for more information on this.