Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: danS on January 11, 2006, 03:19:25 am
-
I am trying to export from EA to import to Tau in XMI format.
The first problem I find is that EA exports using Windows-1252 encoding and Tau doesn't understand this. Is there a way of setting the encoding to ISO-8859-1 that Tau will understand?
I can edit the XML to correct the encoding.
The problem then is that there are duplicate GUIDs in the model that Tau falls over. Is there a setting that will prevent this?
I also tried exporting from Tau, but EA fails to import this as it doesn't like the names exported.
e.g. Tau exports a name
<UML:Parameter xmi.id="i.247.12b3c938" name="alarm.return" kind="return" type="D.class IDecoder&">
Error code 0xc00ce504
char 97
description A name was started with an invalid character
i.e. EA doesn't accept &" at the end of a name.
<UML:Attribute xmi.uuid="C:\workspaces\eatest\eatest3.xml|eaxmiid16" xmi.id="C:\workspaces\eatest\eatest3.xml|eaxmiid16" name="m_listener_list" namespace="C:\workspaces\eatest\eatest3.xml|EAID_6B42EA04_4183_44c7_A1ED_18BA0FE33A4A" visibility="private" type="D.list<IVideoStreamListener*>">
Error code 0xc00ce504
char 267
description The character '<' cannot be used in an attribute value.
i.e. template specialisations can't be used.
Is there any way round this? or are the two systems fundementally different in their interpretation of XMI?
thanks
dan
-
You can set the encoding EA uses by entering it into Tools | Options | XML Specifications | Code Page.
From what you've put there Tau is generating invalid XML.
Ampersand should be represented in an attribute value by its character reference '&', so should '<' ('<')and '>' ('>').
-
Thanks Simon, this sorts out the problem importing the EA model to Tau. There aren't any duplicates either.