Additional Add-Ins

This chapter contains information on the following add-ins:

• Rose Model Integrator Add-In
• ClearCase Add-In
• DDL Add-In
• CORBA Add-In
• Framework Add-In
• Apex Add-In (Not available for Linux)

---

Rose Model Integrator Add-In

The Rose Model Integrator Add-In lets you compare model elements from up to seven contributor files, discover their differences, and merge them into the base model. There are no new features for this release of Rose Model Integrator.

Known Model Integrator Add-In Problems and Limitations

The following table contains known Model Integrator problems and limitations in Rose for UNIX/Linux.

Defect	Description
1236 11454	Model Integrator does not support ClearCase elements. Model Integrator does support ClearCase versions for primary units specified on the command line or in the Contributors dialog, but it does not correctly parse subunit file names to create version-enhanced file names used by ClearCase. The workarounds are: 1. Merge subunit files individually using ClearCase. 2. Create separate views in ClearCase which contain all the proper versions of your model's subunits and then merge the models independently of ClearCase (start Model Integrator in the normal way and enter the model file names in the Contributors dialog). Check the resulting merged model back into ClearCase when you are finished. You will need to create 3 views: the base view containing the previously checked in version, the latest version, and the version you want to merge.
1614	Project specs in Java and CORBA. Directories specified for code generation may not be merged properly into the merged model. The workaround is to reenter these directories in Rose.
2169	Model Integrator allows user to select more than 7 contributors. Model Integrator only allows 7 contributors, but it allows the user to select an 8th contributor and then issues an error message.
7469	Model Integrator creates duplicate model elements. In a situation where one contributor has renamed a model element to new name and another contributor has added the same new name to the model without renaming the old model element, Model Integrator may produce a model with two model elements having the same name. The workaround for this is that when the model is loaded into Rose, Rose will report an error and rename one of the model elements automatically. Visit these elements in the Rose browser window and correct the names of the elements.
18159	In the Contributors dialog, the checkbox for the option "Compare/Merge against Base Model" should be grayed out until two contributors have been added.
25249	Select All does not select the main node in the tree view.

Fixed Model Integrator Defects in This Release

Defect	Description
58683	Model Integrator does not handle unnamed objects properly.
66188	Model Integrator performs merge on unrelated diagrams, which results in a corrupt model. In this case, the diagrams being merged were located in different state machines, different names and UID.

Fixed Model Integrator Defects in Service Release v.2002.05.01

Defect	Description
67981	Rose may crash when selecting 'NewDiagram' once an .mdl file merged by Model Integrator is loaded in Rose.

---

ClearCase Add-In

Note: Prior to using the Rose for UNIX/Linux ClearCase Add-In, it is necessary to review and follow the steps outlined in the README file. Please see the rational_dir/releases/rose.I.J.K/addins/clearcase/README file.

The ClearCase Add-In provides a tight integration between Rational Rose and the Rational ClearCase version control system. This add-in is intended as a replacement for the ClearCase capabilities provided through the previous Rose/ClearCase integration. This has and will continue to allow Rational to provide more ClearCase specific customization to this add-in.

When performing ClearCase actions on a unit in a Rose model, the ClearCase Add-In will now perform CM status checking on all ClearCase elements within the model. This provides an opportunity to perform the same ClearCase action on any element which applies. When the ClearCase dialog is displayed, you will have an opportunity to perform the selected ClearCase action on any or all of the ClearCase elements presented in the dialog. The CM status checking which is performed to provide this new capability can at times seem lengthy if working with a large model. In this case, you may elect not to utilize this feature by placing the following in either your $USER.reg (applies to single user) or the rational_dir/releases/rose.I.J.K/registry/rose.reg file (applies to anyone using the release):

[HKEY_LOCAL_MACHINE\SOFTWARE\Rational 
   /Software\Rose\AddIns\ClearCase\Custom Settings]
"ShowAll"="No" 

Once the registry file is edited the user(s) should run rational_dir/releases/rose/I.J.K/bin/rose_cleanup and then run 'rose' for the change to take effect.

Known ClearCase Add-In Problems and Limitations

The following table contains known ClearCase problems and limitations in Rose for UNIX/Linux.

Defect	Description
15035	When using Rose/ClearCase Integration in Rose for UNIX/Linux, ClearCase output will appear in the terminal used to run Rose in addition to the ClearCase dialogs.
16647	If a user has selected the Rose option of creating back up files but has not selected to create the back up files by copy, Rose may not detect when a newer version of a file has been made available from ClearCase. To project against this, make sure that the Update by Copy option has been selected.

Fixed ClearCase Defects

The following table lists ClearCase Add-In defects fixed since the last release.

Defect	Description
63576	Selecting multiple items and right clicking in the diagram to display context menu, may cause Rose to hang. Workaround: After selecting multiple items in the diagram, use the Tools menu to select option or make selections and right click in the browser.
78647	Rose may hang upon opening ClearCase LT Explorer. Workaround: Close ClearCase LT Explorer in order to use Rose.

---

DDL Add-In

The Data Definition Language (DDL) Add-In release note contains known problems and limitations as well as fixed defects since the last release.

The gap between object technology and relational databases is closed by providing a mapping interface to relational databases through generation of persistent classes to Structured Query Language (SQL) and Data Definition Language (DDL).

You can find DDL Add-In release note information in the following locations:

• Known DDL Add-In Problems and Limitations

Known DDL Add-In Problems and Limitations

There are no known problems and limitations for the DDL Add-In.

---

CORBA Add-In

Rose CORBA Features and Enhancements

The Rational Rose CORBA add-in allows you to forward engineer Rose model elements into CORBA-compliant IDL code and reverse engineer CORBA IDL code into a Rose model.

In support of the CORBA 2.3 Specification, Rose CORBA implements the use of value types. Value types allow you to pass objects by value rather than by reference, which is particularly useful when an object's primary purpose is to encapsulate data, or when you want to explicitly make a copy of an object. Two CORBA stereotypes make use of this enhancement:

• CORBAValue
• CORBAFixed

Known CORBA Add-In Problems and Limitations

The following table contains known CORBA Add-In problems and limitations:

Defect	Description
1770	You can create a nested class in CORBA typedef. You are not supposed to use nested classes in a typedef. This is described in the online documentation for CORBA.
1771	Reverse Engineering reports parse error on comment before }; CORBA reverse engineering reports an error when a comment is added to the last attribute of a struct.
1773	Some Include statements are generated incorrectly.
3881	Rose may hang if a Rose J or CORBA operation and attribute specification dialog box is viewed while the browser is undocked. Rose is unable to gain focus, once the specification dialog is closed.
6478	Nested classes in a CORBA Typedef mnay cause problems during round-trip engineering and are no longer supported. Contact Rational Technical Support if you have any questions.
9664	Syntax Checker should check to see whether a valid modifier is selected before reverse engineering idl.
11721	Unable to create directory over NFS in Java or CORBA Project Specification. Unable to create directory on an NFS mounted disk when defining source directory using Java or CORBA project specification.
16853	Browse source <ctrl+H> or <ctrl+K> shortcut key on CORBA classes fails. It will be necessary to use the CORBA > Browse Code menu option.
57198	Exit sign `x' disabled when the position of the Rose/CORBA Add-In dialog box is moved.

Fixed CORBA Defects in This Release

The following table shows the CORBA Add-In defects that have been fixed since the last release.

Defect	Description
65666	Incorrect package may be created under component view when RE a file that has include statement to other file.
70948	Incorrect IDL code generation for enums.

Fixed CORBA Defects in Service Release v.2002.05.01

Defect	Description
68178	Inheritance may be lost upon reverse engineering.

---

Framework Add-In

The Framework Add-In provides a library of frameworks that can be used as templates when creating new models. There are no new features or enhancements for this version of the Framework Add-In.

---

Apex Add-In (Not available for Linux)

The Apex Add-In of Rose for UNIX/Linux provides direct access to the Compile and Control commands in Apex. It also works with language add-ins for Rose, including Rose C++, Ada 95, and Ada 83 Add-Ins, to create Apex subsystems and views during the code generation from the model to the source files of the specified language.

• It is required to run Rose inside an Apex shell window to use the Apex Add-Ins.
• If the Apex submenu is not in the Tools menu, select Add-Ins > Add-In Manager to make sure the Apex Add-In is activated.

The following information is also located in your Apex Add-In online documentation.

Apex Compile and Control Commands

The Compile and Control commands of Apex are directly accessible from Rose through the Tools > Apex menu. The Compile commands compile and link the source files, generated into Apex views via Apex Add-In, that correspond to the selected items in the diagram. The Control commands perform Apex source code control operations on the source files generated in the same way.

To use these commands, select Tools > Apex, and then select Compile or Control to get to the list of commands, respectively.

For the descriptions on these Apex commands, please consult the online help in the Apex windows.

Code Generation With Apex Add-In

In general, the code generation operation for a regular language Add-In is based on a directory structure where top-level packages, nested packages, and classes (or modules) are mapped, respectively, into directories, subdirectories, and source files in a hierarchical way. The operation can create such directories or subdirectories if they do not already exist, and then generate source files into these (sub)directories. This works with the regular source code control system and build management.

Apex has a different style of source code control and build management. An Apex project has a set of subsystems which contain the source files and subdirectories of source files for development. Each developer has his own views, one for each subsystem, which collectively reflect the source base the developer uses for the project. For this reason, Apex-style code generation is different from the regular style. From a Rose model, the top level packages will be mapped into subsystems and the associated views for the developers; the packages nested inside another package will be mapped into the subdirectories inside an Apex view, or a subdirectory already enclosed by a view; the classes (or modules) will be mapped into the source files inside the views or the subdirectories.

The Apex Add-In provides a mechanism for the user to select which of the two code generation styles to use. When the property CreateApexSubsystemAndView of the Apex tool set is set to "Yes", the code generation command for a language add-in will automatically create Apex subsystems and views for the top-level packages selected in the model, followed by the generation of subdirectories and source files into the views. If the property is not set to "Yes", the code generation command does the regular style of code generation.

The language add-ins that work with Apex Add-In include C++, Ada 95, and Ada 83.

Properties for Apex Add-In

Refer to the online documentation for a list of the properties used by the Apex Add-In for Apex-style code generation. Some are properties for the project, and the others for the subsystems in the model. The code generation command will use the combination of these properties when it needs to generate code into Apex subsystems and views.

All the properties except CreateApexSubsystemAndView will take effect only when the CreateApexSubsystemAndView property is set to "Yes" and when the selected item is a top-level package. When any of these properties are specified differently from their default value, the Directory property for the top-level package should remain as the default value.

Utilizing Apex Add-In on HP-UX and SGI IRIX

In order for Apex to generate subsystems correctly, it is necessary for "tmp-mnt" to be placed in the automount field of the Virtual Pathmap dialog box. The "/tmp-mnt" entry should be removed from the Virtual Pathmap dialog box when not using Apex.

Utilizing Apex Add-In on AIX

When using the Apex Add-In to create Apex subsystems and views on AIX, Rose for UNIX/Linux might run into a hanging state. If that happens, look for an Apex "Job Queue" window. In that window, select all the entries and click File > Run Job. This will resolve the "hanging" state and resume code generation.

Known Apex Add-In Problems and Limitations

The following table shows known defects in the Apex Add-In.

Defect	Description
3853	CM commands do not show on the context menu for packages in the browser. When this occurs, you are unable to use Apex CM integration on a package that does not appear in the diagram. Workaround: Add the package to the diagram.

Rose Ada Defects Fixed in This Release

Defect	Description
14965	Rose/Apex needlessly reports circularities among nested packages,
16142	Private Only visibility for code generation of operations required.
69859	Ability to specify a text file in the Copyright notice property required.
71327	Ability to control the order of code generation in a package required. A new (attribute,has,role) property Declare=(Before,After) can be used to control where the static declaration should be declared - either before or after the class type.
74511	Wrong signature generated in the Generic Subprogram Body.
75639	Rose Ada: System Error: line 10811, pc 27607 Null Handle in request for property "inherits".

Fixed Defects in Service Release v.2002.05.01

Defect	Description
29061	Rose/Ada does not support RUP component view mapping.