Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363160 - Texo: specifying order-by leads to invalid orm.xml
Summary: Texo: specifying order-by leads to invalid orm.xml
Status: VERIFIED FIXED
Alias: None
Product: EMFT
Classification: Modeling
Component: Texo (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Martin Taal CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-08 06:42 EST by Peter Kullmann CLA
Modified: 2011-11-09 03:19 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Kullmann CLA 2011-11-08 06:42:46 EST
I have a multi-valiued reference which is realized as a List: 

      <orm:one-to-many name="vorgaben" orphan-removal="true" target-entity="ch.arenae.phoenix.domain.security.Benutzervorgabe">
        <orm:order-column/>
        <orm:join-column/>
        <orm:cascade>
          <orm:cascade-all/>
        </orm:cascade>
      </orm:one-to-many>

In the annotation model i set the property "Order by" on the "One To Many" element to "nummer ASC". 

Texo generates this (EclipseLink ORM):

      <orm:one-to-many name="vorgaben" orphan-removal="true" target-entity="ch.arenae.phoenix.domain.security.Benutzervorgabe">
        <orm:order-by>nummer ASC</orm:order-by>
        <orm:order-column/>
        <orm:join-column/>
        <orm:cascade>
          <orm:cascade-all/>
        </orm:cascade>
      </orm:one-to-many>

This is not valid. It should not include the order-column field if order-by is specified.        
I was using Texo version 0.1.0.v201109262010.
Comment 1 Martin Taal CLA 2011-11-08 12:14:14 EST
Solution available in latest build, can you try it?
gr. Martin
Comment 2 Peter Kullmann CLA 2011-11-09 03:19:02 EST
Thanks! Works very well. That was fast! 

(Pity you couldn't make it to ece2011)