Author Topic: XMI 2.1  (Read 3977 times)

gericson

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-1
  • I love YaBB 1G - SP1!
    • View Profile
XMI 2.1
« on: April 13, 2006, 10:12:42 am »
I attempted import of XMI for Superstructure and Infrastructure from the source posted at http://www.omg.org/cgi-bin/doc?ptc/06-04-07.  I renamed .cmof extensions to .xmi extensions.

EA 6.1 build 789 complains about "Unknown XMI exporter or version."

Is there a work-around, or a date for support of XMI 2.1?


George

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: XMI 2.1
« Reply #1 on: April 13, 2006, 10:30:29 am »
Make sure the appropriate DTD is in the same file as the XMI source. With the files from OMG it is always best to check that they actually validate against the DTD provided. I have not had significant problems with recent XMI files from OMG, but each of the older metamodel files I've gottem from them has failed to validate against the appropriate DTD. In some cases no DTD was provided (broken links etc.) but the XMI file failed to validate against any DTD, often producing hundreds of violations.

If this does not work, I doubt you will find an effective workaround at this time.

Now the good news: XMI 2.x support is coming. Best guess is that it will be part of EA 6.5, which looks to be coming fairly soon. My guess is later this Spring or very ealry Summer, but that's only a guess.

David
No, you can't have it!

meierch

  • EA User
  • **
  • Posts: 35
  • Karma: +0/-0
  • Modeling we can!
    • View Profile
Re: XMI 2.1
« Reply #2 on: December 18, 2006, 12:38:24 pm »
I just tried to import th CMOF / XMI files as well but that did still not work. Who has done that with EA so far?

Christian
Regards
Christian

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8083
  • Karma: +118/-20
    • View Profile
Re: XMI 2.1
« Reply #3 on: January 01, 2007, 03:16:45 pm »
I've had a brief look at the files mentioned.  It looks like they aren't importing because they aren't UML XMI.  EA supporting importing XMI 2.1 for UML 2.0 and UML 2.1.  It doesn't currently support importing XMI 2.1 for MOF which is what these files are.

You can import the files into EA, although I've been told that generalizations are currently lost with the method I'm about to suggest.  (A more complex transformation would be required to fix this)

Copy the XMI header, documentation and uml:Model from an EA UML 2.0 (XMI 2.1) export and replace the root of the cmof document with these.

Replace all xmi:type values (currently in form cmof:????) with uml:????.