Skip to main content
diff options
authorVincent Lorenzo2017-01-13 09:13:15 -0500
committerGerrit Code Review @ Eclipse.org2017-01-18 06:51:49 -0500
commit8aa6e885a1c748556f2c024e8b14af522a0f8f77 (patch)
tree4d542d84a79ac338a5981965b0579499e6f2ebd0 /plugins/doc
parentd9e7dcac172e360eb053c4cff35479e801d8e760 (diff)
Bug 508513: [Importer][Rhapsody] Rhapsody Types libraries used in a Rhapsody Model should be imported too
Change-Id: Ieae5c2976be3af776c9f8099f2c24249e98a0e9e Signed-off-by: Vincent Lorenzo <>
Diffstat (limited to 'plugins/doc')
2 files changed, 3 insertions, 5 deletions
diff --git a/plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc/src/site/mediawiki/rhapsodyMigrationDev.mediawiki b/plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc/src/site/mediawiki/rhapsodyMigrationDev.mediawiki
index 8cb9ab68bb9..65d7208df22 100755
--- a/plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc/src/site/mediawiki/rhapsodyMigrationDev.mediawiki
+++ b/plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc/src/site/mediawiki/rhapsodyMigrationDev.mediawiki
@@ -52,6 +52,7 @@ JUnit tests are provided too. They use EMF-Compare to check that the imported mo
The migration process is done in 3 steps:
#the ''*rpy'' file is parsed by the XText parser (plugin '''org.eclipse.papyrus.migration.rhapsody.parser''') and converted into a first simple model using a first EMF metamodel, '''RpySyntax''', provided by this plugin, then
#this first model is converted into a set of ''*.umlrhapsody'' by the class '''org.eclipse.papyrus.migration.rhapsody.importer.UMLRhapsodyImporter'''. There is a ''*.umlrhapsody'' file for the intial selected ''*rpy'' file, and one other for each dependency of the Rhapsody model (SysML, PredefinedTypes, ...)/
+#the ''*.umlrhapsody'' files representing a Rhapsody Library owns a EAnnotation at the root of the file, indicating they are Rhapsody Library.
#the ''*.umlrhapsody'' files are converted into a Papyrus model.
==What is the purpose of the UMLRhapsody metamodel?==
diff --git a/plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc/src/site/mediawiki/rhapsodyMigrationUser.mediawiki b/plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc/src/site/mediawiki/rhapsodyMigrationUser.mediawiki
index d8a467e9962..ea4c913ba04 100755
--- a/plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc/src/site/mediawiki/rhapsodyMigrationUser.mediawiki
+++ b/plugins/doc/org.eclipse.papyrus.migration.rhapsody.doc/src/site/mediawiki/rhapsodyMigrationUser.mediawiki
@@ -179,11 +179,8 @@ The following stereotypes are supported (not complete list).
===Properties's Type Mapping===
-Several mapping are possible depending on the case, here the list, by order, of these mappings:
-*the type is defined in the Rhapsody model too, we map it with the corresponding UML element created by the transformation.
-*the type is a primitive type which can be mapped on a type defined in the UML Primitives Types library, so we reference it.
-*the type can be mapped with a C++ type defined in the Papyrus Designer library, so we referenced it
-*the type can't be mapped on an existing element, in this case, we create a Class, with the name of the type. This class will be stored at the root of the UML Model file, and a message will be displayed in the '''Log''' during the mapping process.
+* The Rhapsody Types Libraries (like PredefinedTypes, PredefinedTypesC and PredefinedTypesCpp) are imported, when required, as UML Package in the imported Model. By this way, the types of the user model are preserved by the transformation.
+* To ease user experience, we always import the UML Predefined Types library, but we doesn't use the provided types in the imported model.
===Diagram Mapping===
*Papyrus Rhapsody Migration Tools allows to import Rhapsody SysML Diagrams as Papyrus SysML 1.1 Diagrams. The supported diagrams are:

Back to the top