dynamobi/enki — Issue #4: [ENK-6] Attribute and Associations are generated in different orders across JVMs
Author: dynamobi-build
Created: 2011-12-30 02:07:10+00:00
State: open
Labels: ENK

[reporter="stephan", created="Fri, 5 Dec 2008 18:58:33 -0500 (GMT-05:00)"]
Attribute and Associations are generated in different orders across JVMs.

Attribute parameter ordering in factory methods for class proxies vary across JVMs. This happens intermittently. See IceCreamCone references in ENK-3. In general, this likely means the Attributes are varying in order as well. It should only be visible for a) the factory methods already mentioned, and b) for event ordering for Attributes with a type that is a Classifier from the model itself.

Associations are generated in varying orders across JVMs as well. This happens more regularly and causes the MdrEventApiTest failure seen with the Sun JDK -- the eem.sample.special.Floor is firing events in order of associations found in the model and since the test requires it to fire events for two associations, reversing them causes the exception. (Also noted in ENK-3.)

Paths of investigation:

- Is this caused by XSLT output variation across JVMs? If so, is the variation unexpected (e.g., is the re-ordering ordered elements in the XML an XSLT script or XSLT processor bug) or expected (in which case can XSLT be modified to maintain order or should code gen sort the objects)

- If XMI input is constant, is MDR re-ordering elements that it shouldn't or is it Enki code gen?