1. Import the UML 1.4 metamodel into a new MOF extent.
2. Go to Data_Types::UnlimitedInteger
3. Switch the look on UnlimitedInteger to the
reflective view
4. Expand the "contents" node.
5. Expand the "type" node.

You will see the following:
package Data_Types {
   ...
   alias type Integer : PrimitiveTypes::Integer
   alias type UnlimitedInteger :
UnlimitedInteger::Integer
   {
      alias type Integer : PrimitiveTypes::Integer
   }
   ...
}

(a) The UnlimitedInteger alias type contains an
extra alias type that should not be there at all
(Data_Types::UnlimitedInteger::Integer)

(b) The UnlimitedInteger's type is set to be this
extraneous alias type (the correct type is
Data_Types::Integer).

This problem affects also the CWM metamodels.
Apparently it only happens when an alias type's
type is another alias type. For example,
Data_Types::String correctly references
PrimitiveTypes::String.

I believe that the faulty code is
XmiContent.resolveCorbaAlias(Node node).