Importing a J MDA component for redefinition

Importing a J MDA component

J MDA components can be imported into MDA Modeler for redefinition in the form of model components (with the ".ramc" extension). This redefinition can take the form of the addition of new extensions or the definition of a new implementation of an existing J MDA component, for example.

A J MDA component must already have been deployed in your project before being imported as a model component. For more information on deploying MDA components, please see "Working with MDACs".

After deployment, a Java MDA component (in its model component form) is located in the "objing_path/mdaplugs/MDAC_name/x.x.xx/mdamodel" directory.

To import a J MDA component, carry out the following steps:

1. Click on “Import an MDA component …” in the “Extensions” menu. The window shown in Figure 172 below then appears.

Figure 172. The "Deploy a model component" window, used to import a J MDA component

2. In the "Path" field, click on the browser icon on the right to browse and select the J MDA component you want to import.

3. Click on “Deploy” to confirm. The selected J MDA component is then immediately imported.

Dependencies to other model components

J MDA components depend on the "core" and "metamodel" model components. This means that these must already be deployed before you import a J MDA component.

The "metamodel" model component is automatically deployed when MDA Modeler is deployed in your project. It is located in the "objing_path/mdaplugs/MDAModeler/x.x.xx/models" directory.

The "core" model component is automatically deployed when a J MDA component is created. It is located in the "objing_path/mdaplugs/MDAModeler/x.x.xx/models" directory.