Book a Demo

Author Topic: Export UML2.1 - XMI 2.1 : irregularities  (Read 5936 times)

mia

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Export UML2.1 - XMI 2.1 : irregularities
« on: March 19, 2008, 03:40:34 am »
Hi,
Using EA 7.0, I've exported my model in UML2.1 - XMI 2.1 and I've found 2 irregularities regarding the MOF UML2.1 specifications.
Some instances of "FinalNode" are exported while it is an abstract type.
Some instances of "ObjectNode" are exported while it is an abstract type.
Seems to be a bug, doen't it ?
Thanks,

Mia-Software

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Export UML2.1 - XMI 2.1 : irregularities
« Reply #1 on: March 19, 2008, 03:52:04 am »
Check the UML XMI specification.
No, you can't have it!

mia

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Export UML2.1 - XMI 2.1 : irregularities
« Reply #2 on: March 20, 2008, 01:15:51 am »
Does the UML XMI specification authorize to create instances of abstract types ?!!
I don't think so !
FinalNode is abstract and has two concrete subtypes ActivityFinalNode and FlowFinalNode.
Instances of FinalNode should not be found in an exported xmi file...
Neither intances of ObjectNode...

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Export UML2.1 - XMI 2.1 : irregularities
« Reply #3 on: March 20, 2008, 06:48:58 am »
Well, I took the time to look.

This was definitely allowed in XMI 1.x. I can find no prohibition in 2.x, particularly in the UML variant.
No, you can't have it!

mia

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Export UML2.1 - XMI 2.1 : irregularities
« Reply #4 on: April 03, 2008, 04:52:19 am »
Here is the answer of your support :
"Regarding exporting the Activity Final Node:
EA currently exports this node a "uml:FinalNode" instead of "uml:ActivityFinalNode". This is a bug and we will have this issue fixed in the next release of EA.
  
Regarding "ObjectNode" :
EA should not allow creating an "ObjectNode" directly as it is an abstract class. We will have this issue fixed in the future releases of EA.
Hope this clarifies your issue. If you have any further queries, feel free to write-in.
Best Regards,
Vimal Kumar
Sparx Systems Pty Ltd"

Thank you Vimal