This applies to CWM 1.1 (and also CWM 1.0).
Sun MDR user Vincent Lombart spotted that he was getting the same
association exported twice, which I tracked down to the following problem in
There should be no explicit association between ClassifierMap and
TransformationMap: the diagram in the CWM spec just documents the fact that
the inherited ownedElement association is used to link these classes.
The CWM XMI file is produced by the Unisys Rose integration which explicitly
ignores such associations (signalled by '/' on the association ends - normal
derived associations have '/' on the association name). This is used in
several places e.g. in Relational model to show that Column and ColumnSet
are linked using the owner-feature association.
However in the ClassifierMap case there are also corresponding references
explicitly defined as pseudo-attributes on Classifier and TransformationMap
which has caused the references erroneously to be generated into the XMI
On further investigation, the following inherited associations have
XML:ElementType <-> XML:Schema
XML:ElementType <-> XML:Attribute
Transformation:TransformationMap <-> Transformation:ClasifierMap
Transformation:TransformationActivity <-> TransformationStep (in this case
the references are called 'step' and 'activity')
BusinessNomenclature:Taxonomy <-> Concept
BusinessNomenclature:Glossary <-> Term
BusinessNomenclature:BusinessDomain <-> Taxonomy (in this case one
reference is called just 'domain')
Delete the above references/pseudo-attributes (with stereotype of
<<reference>> though this is hidden on the diagram).