| Texo: list of annoying details [message #872963] |
Thu, 17 May 2012 03: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.
|
|
|
Powered by
FUDForum. Page generated in 0.01717 seconds
] 
Search
Help
Register
Login
Home
