Before you begin the process of importing Rational XDE™ Java™ code
models, it is important that you understand the main Java code
model migration limitations.
The XDE Java code
model import process has the following limitations:
- The import process is a one-way procedure; once you import a model into
the Rational® UML
modeling products, you cannot bring the imported model back into XDE. The XDE
Java Project Import wizard uses a lot of memory during the model
import process.
- Typically, you can expect the import wizard to use 1.25 times the amount
of memory normally used to load the imported model in XDE. If you notice memory
issues while working with the model in XDE, it is likely that you will encounter
memory issues during the import process.
- Although compare and merge is not important during the model import process,
it may be important for ongoing use of the imported models once migration
has been completed.
- XDE Web
models, EJB models, and J2EE Deployment models cannot be migrated. The Rational UML
modeling products use an entirely different approach to support Web and J2EE
development, based on the use of Web-specific and J2EE-specific modeling languages
and no use of UML. Before attempting migration from XDE you must ensure that all XDE content models
and Java code
models are updated to remove any cross-model references that resolve to these
type of models. Such references will typically exist only as a result of having
depicted elements from those models, on diagrams that are stored within the
content models and Java code models.