Re: [mdr-users] Ordering vs. isOrdered attribute on UML:AssociationEnd

UML 1.4 metamodel defines "ordering" attribute. I believe EA is using 
UML 1.3 rather than UML 1.4. It is possible that in UML 1.3 there is 
isOrdered instead of ordering. MDR has no special support of UML - you 
just load in any metamodel you have and can immediately work with it. If 
some XMI produced by a tool cannot be read by MDR into an instance of a 
given metamodel, then it means the XMI does not really conform to that 
metamodel.
Regards,
Martin

Lars Ködderitzsch wrote:

> Hi all,
>
> this is my first post on this list - so please excuse me if this has 
> already been discussed.
> I am playing with AndroMDA (which uses Netbeans MDR) and I stumbled 
> over an issue with the ordering/isOrdered attribute on an 
> UML:AssociationEnd.
> Enterprise Architect uses the isOrdered attribute in its exported XMI 
> (1.2).
> This is not regognized by the MDR.
> Other tools (like MagicDraw) use and ordering="ordered" attribute to 
> mark an AssociationEnd ordered.
> This is perfectly recognized by the MDR.
>
> After a quick look into the XMI 1.2 spec over at OMG I a tempted to 
> say that EA is (in this case ;-) ) right using the isOrdered attribute.
>
> Right now I am using an XSLT-Stylesheet to "fix" this issue so I can 
> use the EA exported XMI with AndroMDA.
>
> Is this problem known?
>
> With best regards,
> Lars Ködderitzsch