[BUG] xmi export has a bug

[HarryMuc]

hey y'all!

I think I just found a (small but - for me - annoying) bug. I use EA to design a model and export it to XMI which I further process with another tool. In my model, I have tagged values attached to a package. This reference isn't exported correctly.

The package has the xmi.id "EAPK_..." while the tagged value references the id "EAID_..." so the tool can't associate the tagged value with the package b/c the ID is wrong.

Maybe you can fix this in the next version. Currently, I edit the xmi file manually before further processing it by replacing the xmi.idref by "EAPK_...".

If it's important: I use 4.50.744 and export the XMI file in Unisys/Rose Format.


Thanks,

-- Harry

[thomaskilian]

http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=Latest;action=display;num=1107906615;start=0#0

[HarryMuc]

I read through the changelog and didn't find anything relevant?! However, I just downloaded the latest version and it still references "EAID_..."

<Foundation.Core.ModelElement xmi.idref="EAID_6D0BD6D6_B039_4af0_955D_D1C0309BE918"/>

<Model_Management.Package xmi.id="EAPK_6D0BD6D6_B039_4af0_955D_D1C0309BE918">

[thomaskilian]

It was just because the change log told something about XMI and tags and the build was younger than yours. But since your problem still exists - no idea :-/

[VK]

Hi HarryMuc,

I could not reproduce your problem.

When I exported the package to Unisys/Rose Format XMI 1.0, and imported them in Poseidon and MagicDraw UML (I am not sure what tool you are using), I could get the tagged value of the package correctly. Also, when I checked the XMI file, the tagged values for the package are being referenced as 'EAPK_' and not 'EAID_'.

So, if you could send in a sample model which reproduces your issue, it would help me in correcting the bug.

You can send the model to : [email protected]

Cheers