PIM2PSM transformation transforms wrong classifier

[Oliver F.]

Here is another (crtiical) bug I submitted:

===============
Several classifiers might be available with the same name in different hierarchies of the model.
Eg. take the following example:

Code: [Select]

class C1
{
     attribute1: package1.classifier;
}

class C2
{
   attribute2: package2.classifier;
}
The classifier in C1 is indeed another object than the classifier of C2- it just resides in different locations of the model but has the same name. The classifiers can be correctly chosen from the types dialog.
However during a transformation to a PSM (eg. by using the Java template) the classifiers are not identified correctly and, depending on the order in the model, the transformed attribute2 is transformed to have package1.classifier as type.
Propably a getbyname is applied and the first one found is chosen instead of correctly choosing the appropriate ClassifierID.
This is a highly critical bug as it completely spoils our transformation.
=========================

Oliver