Book a Demo

Author Topic: EA x MDR UML2MOF  (Read 2729 times)

andreok

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
EA x MDR UML2MOF
« on: May 18, 2005, 07:35:26 pm »
Does anybody uses the EA to generate metamodel UML XMI 1.2 files and then convert it to MOF XMI using NetBeans MDR UML2MOF tool?

I'm having some problems I think related to TaggedValues compatibility. The EA UML XMI 1.2 exported file associates the TaggedValues values under a UML:Collaboration tag, but the MDR example file associates the TaggedValue values under the owner element. I don't undertand why EA generates a UML:Collaboration tag to place the TaggedValue value inside.

I found a comment in the Topic: Version 4.1 - Build 739 Released saying that "Resolved some compatibility issues in XMI 1.2 export to support Netbeans MDR (using uml2mof).", but I couldn't find exactly what compatibility issues it's about.

kpetrov

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: EA x MDR UML2MOF
« Reply #1 on: June 28, 2005, 01:16:44 pm »
Any luck?
Actually when I export xmi 1.0, Poseidon eats it but I thought that Poseidon is 1.2 compliant. Isn't it the case?

andreok

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: EA x MDR UML2MOF
« Reply #2 on: June 28, 2005, 01:33:00 pm »
No.

I was reading the Netbeans MDR forum and I found the
following topic:
"> >>From: Martin Matula [mailto:[email protected]] >>Sent:
> Friday, July 02, 2004 10:02 AM
> >>To: [email protected]
> >>Subject: Re: [mdr-users] Enterprise Architect and MDR
> >>
> >>Hi,
> >>this looks like a consequence of a famous bug in the UML 1.3 XMI
> DTD >>available from OMG. The problem is that the  UML 1.3 DTD
> >>allows you to >>have taggedValue elements under an UML model
> element. However >>from MOF >>and XMI point of view this is not
> possible since UML 1.3 >>metamodel does >>not define taggedValue
> reference in ModelElement. So, the DTD >>does not >>match the UML
> 1.3 metamodel. Unfortunatelly many tool vendors >>implemented the
> XMI export purely based on the DTD. This is >>how this bug >>got
> into several UML tools that support XMI export and made it
> >>impossible to import these XMI files into the tools that enforce
> XMI >>correctness based on the UML metamodel rather than just the DTD.
> >>One way how you could try to solve it is to remove all
> >><UML:ModelElement.taggedValue> elements from your XMI.
> >>Also please make sure you load the UML 1.3 metamodel into MDR
> using >>the >>XMI diff file available from
> http://mdr.netbeans.org/metamodels.html.
> >>Regards,
> >>Martin"

As described in the topic there's a compatibility issue caused by a specification incompatibility.