Importing XDE Java modeling projects process overview

You must complete four high-level steps to migrate an XDE™ Java™ modeling project successfully. You can find detailed information about each step in the XDE Java Project Import wizard online help.

To completely import an XDE Java modeling project, you use two separate wizards. First, you use the XDE Model Import wizard to convert XDE model (.mdx files) into .emx files. Then, you use the XDE Java Project Import wizard, to re-establish the original links between the model and the code in the Rational^® XDE Java modeling project.

To import XDE Java modeling projects:

Import all the XDE models (.mdx files) that the project needs by using the XDE Model Import wizard. Specifically, make sure to import the code model within the project.
To avoid a naming conflict when you import files, make sure that the destination project has a different name from the original XDE Java project.

Attention: To avoid data loss or synchronization issues, do not modify the XDE model, the imported model, or the related source code before you import the Java project.
Import the XDE Java project by using the XDE Java Project Import wizard. This wizard modifies the .project file so that it is compatible with Eclipse after import.
Some XDE projects are more complex than others because of varied file encoding. If a project contains files with different encoding, you might need to import the project through the Import Existing Project into Workspace Eclipse command and specify the correct encoding.
Determine which Design Contract Management protocol to use. The protocol you choose determines which option you select in the XDE Java Project import wizard. For details about the various Design Contract Management protocols, see the Welcome pages associated with this product: click Help > Welcome.
Establish the original links between the model and the code in the Rational XDE Java project by using one of the following methods:
- UML elements in the imported XDE Java code model are replaced by direct references to the corresponding elements in the Java source files. In diagrams, elements continue to appear as class shapes, but, they semantically represent Java instead of UML. With this option, migration results in a configuration of models and code that is ready to use with the Mixed Modeling Design Contract Management protocol.
- UML elements in the imported XDE Java code model remain UML elements. Code elements in the Java source files can be tagged as part of the code model import process to reflect the synchronization option in the original XDE base model. The wizard appends @generated tags to all the code elements in the Java source files for which synchronization was enabled in the original XDE model (by setting the Round-Trip Engineering Synchronization policy to Synchronize, Accept code changes, or Accept model changes).
  After import, the configuration of models and code is ready to use with the Architecture Reconciliation, Conceptual Models Drive Development, or Design Contract Management protocols. In this case, after the import process is complete, the code elements that were not tagged (based on the value of the Synchronize property in XDE) are not deleted or overwritten by the UML-to-Java 5 transformation.
Right-click the generated transformation configuration file (.tc) and select Transform > UML to Java V5.0 before making any changes to the imported model or code.