Re: [mdt-papyrus.dev] Where is the code generator for diagram tests?

[Sergey Boyko <serg.boyko2011@xxxxxxxxx>]

Hi Christian,

For multivalued features that are inherently unordered (like Package::packagedElement in UML.ecore) Ed W. suggested to use  ->sortedBy(...)  function.  For example packaged elements can be sorted by names.

Surely not every access to packagedElement should be sorted but only the result collections that are stored to intermediate model(s).

Regards,

  Sergey Boyko.

On Wed, Apr 15, 2015 at 3:46 PM, Christian W. Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Juan,

Thanks for your feed-back.  I’m glad to hear it, especially since it seems to align so well with my own inclinations.  :-)

I don’t think there was a problem with the ordering of the features of classifiers.  The main problem stems from Package::packagedElement, which is (understandably) unordered.  The intermediate models in this transformation pipeline make heavy use of packaged elements:  the test-context classes, of course, but more importantly the InstanceSpecifications in the UML representation of the GMFGen are all randomly ordered.

Cheers,

Christian