Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 363160

Summary:	Texo: specifying order-by leads to invalid orm.xml
Product:	[Modeling] EMFT	Reporter:	Peter Kullmann <peter.kullmann>
Component:	Texo	Assignee:	Martin Taal <mtaal>
Status:	VERIFIED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:

Description Peter Kullmann

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

2011-11-08 12:14:14 EST

Solution available in latest build, can you try it?
gr. Martin

Comment 2 Peter Kullmann

2011-11-09 03:19:02 EST

Thanks! Works very well. That was fast! 

(Pity you couldn't make it to ece2011)