Bug 34752

Association links that are not serialized by means of 
object references are represented in XMI by separate 'link 
elements'. These elements get the name of their association 
proxy as tag name. XMIWriter produces this tag name 
incorrectly.
The defect was observed using MDR 0.87, JMI Toolkit 0.77, 
UML 1.3 (OMG document 01-12-02.xml). The error can be 
reproduced by attaching an instance of metaclass 
TaggedValue to an instance of metaclass Class (i.e. 
UmlClass). The name of the association is 
AModelElementTaggedValue. There is only a reference for the 
association in metaclass TaggedValue. The association end 
at metaclass Class is composite. Both metaclasses are 
located in different metapackages. A simple example for 
this is:

<UML:Class xmi.id = 'a1' name = 'Testclass' visibility 
= 'public' isSpecification = 'false'
  isRoot = 'true' isLeaf = 'true' isAbstract = 'false' 
isActive = 'false'/>
<UML:TaggedValue xmi.id = 'a2' tag = 'persistence' value 
= 'persistent'/>
<UML:Extension_Mechanisms.A_modelElement_taggedValue>
  <UML:Class xmi.idref = 'a1'/>
  <UML:TaggedValue xmi.idref = 'a2'/>
</UML:Extension_Mechanisms.A_modelElement_taggedValue>

The tag 
name 'UML:Extension_Mechanisms.A_modelElement_taggedValue' 
is not correct and should 
be 'UML:A_modelElement_taggedValue'

The resulting XMI is not accepted by XMIReader.