Eclipse Community Forums: Ecore Tools » Texo: list of annoying details

Help

Home

Home » Modeling » Ecore Tools » Texo: list of annoying details

Show: Today's Messages :: Show Polls :: Message Navigator

Texo: list of annoying details [message #872963]

Thu, 17 May 2012 07:35

Olaf Burdziakowski

Messages: 46
Registered: April 2012

Member

I work for a while with Texo. I find it very useful but there are some annoying details. I do not know if these are bugs or "features", please clarify:

1.I set prefix to empty in my ecore model. (nsPrefix=""). Then I generate code (Generate JPA annotated model code). I got model new code with copy of my ecore model where the prefix is again default. I have to enter and clear it again.

2.Annotation model editor shows 'inverseJoinColumn' as 'joinColumn'. So such structure:

<joinTable name="DPL_creconfig_GroupType_creditingMeasure">
<joinColumn name="gr_id"/>
<inverseJoinColumn name="cm_id"/>
</joinTable>

Is shown as two joinColumns instead joinColumn and inverseJoinColumn

3.Texo generate such code:
@JoinColumns({ @JoinColumn(name = "condition") })
private VarConditionType condition = null;

The "condition" is restricted for hibernate and do not work. I wanted to annotated this as: "_condition":
<eClass href="cre_config.ecore#//VarInputType"/>
<annotatedEStructuralFeatures xsi:type="annotationsmodel:AnnotatedEReference">
<eReference href="cre_config.ecore#//VarInputType/condition"/>
<eReferenceAnnotations xsi:type="ormannotations:EReferenceORMAnnotation">
<joinColumn name="_condition"/>
</eReferenceAnnotations>
</annotatedEStructuralFeatures>
This do not works .... Still code has "condition" instead of "_condition"

4. Eclipse has a problem with recognizing updates of xsd model from external tools, (and refresh in Eclipse - F5): sometimes I have to restart Eclipse to force Texo regenerate code properly. Example: delete ecore model. Recreate ecore model. Genarate JPA annotated code. The code was generated without noticing annotationmodel file. Restart of Eclipse helps.

Report message to a moderator

Re: Texo: list of annoying details [message #1061530 is a reply to message #872963]

Sun, 02 June 2013 08:20

Martin Taal

Messages: 5468
Registered: July 2009

Senior Member

Hi,
A very old thread, still I tested some things:
1) Texo always assumes that the nsprefix is set, so although you maybe right that an empty nsprefix is not handled correctly, it is an unsupported case
2) I tested this and it works fine in the current Texo version
3) I tested this and it works fine in the current Texo version
4) I could not directly reproduce now, but this can all be because of my environment, I remember to have solved an issue where the epackage was somehow cached in the eclipse memory, so re-generation would use older versions, but not sure if this applies here.

gr. Martin

Report message to a moderator

Previous Topic:	[TEXO] getting started with texo.web.example
Next Topic:	Ecore Model Does Does Not Create

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 24 23:55:45 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter