XMI export of Components and import to a new project results in classes.

You need to have the option "Export Rhapsody Profiles" selected.

When the option “Export Rhapsody Profiles” is not selected, the produced xmi file does not contain required data that is relative to Rhapsody itself.  Rhapsody can model some concepts that are not UML. For handling this situation, a profile dedicated to Rhapsody is provided by default inside the model. And all elements that require to express something that cannot be defined in UML are applying stereotypes from this Profile.

This data can be used for two purposes: getting specific data from Rhapsody that cannot be expressed natively in UML, and keeping this data when roundtripping Rhapsody->UML->Rhapsody.

A Rhapsody Component cannot be expressed directly in UML (there is the concept of Component, but it does not matching the one from Rhapsody). So a Rhapsody Component is exported as a Class, and a stereotype is applied on it for specifying its real nature.

By not selecting “Export Rhapsody Profiles”, you forbid the usage of this profile.