Modeling - release notes


1.0 Known problems
   1.1 Default does not permit number sign (#) in file names for model files
   1.2 The product does not support the question mark (?) in file names of model files
   1.3 Models do not open if stereotype property names contain invalid characters
   1.4 Connectors might intersect model elements in published models
   1.5 Icons in titles of model elements do not print properly
   1.6 Dependency and realization connectors might not be visible in printed models
   1.7 Cannot visualize non-composite properties in composite structure diagrams
   1.8 Copying and pasting from the file system might corrupt models
   1.9 Cannot easily add parameters or return types for behaviors
   1.10 Properties might not update immediately on the Properties page
   1.11 The Model Explorer view might not display stereotype names
   1.12 Cannot add stereotypes to multiple elements at one time
   1.13 Classes might not appear as cross-model references
   1.14 Model connections might not update properly in the diagram editor
   1.15 Show related elements option is not available for state elements
   1.16 The Model Explorer view might not properly indicate unsaved changes
   1.17 Certain menu items do not appear on the Add UML pop-up menu
   1.18 Default information in the Inheritance Explorer view is misleading
   1.19 The product might display validation error messages that are not descriptive or useful

1.0 Known problems

1.1 Default does not permit number sign (#) in file names for model files

By default, you cannot use the number sign (#) in file names for model files. The model files do not open.

To use the number sign character in model file names, open the <install_dir>/rationalsdp.ini file and add the following argument under the Settings section:

VMArgs=-Dorg.eclipse.emf.common.util.URI.encodePlatformResourceURIs="true"

Note: Do not add this argument to an already existing line. This argument should be on its own line in the file.

1.2 The product does not support the question mark (?) in file names of model files

On Linux operating systems, a file name can contain a question mark (?). However, Rational Software Architect does not support question marks in model file names. If you use a question mark in a model file name, an exception is thrown in the .log file. Do not use question mark characters in model file names.

1.3 Models do not open if stereotype property names contain invalid characters

If you apply a stereotype to an element in a model, and then modify a property that the stereotype added to use blank spaces, after you save and close the model, you can not open the model. To avoid this issue, use the underscore character (_) instead of spaces in the names of stereotype properties.

To work around this issue, use a text editor to remove the name value pair that is associated with the property. For example, you would remove the "My Stereotype Property" property from the following example:

 <contents xmi:type="Profile_2:Profile__Stereotype1" xmi:id="_eVPvkCbPEdmF27ugxgyz4g" My Stereotype Property="New Value"/> 

If you remove the property, the result would be as follows:

 <contents xmi:type="Profile_2:Profile__Stereotype1" xmi:id="_eVPvkCbPEdmF27ugxgyz4g"/> 

1.4 Connectors might intersect model elements in published models

When you work with a UML model, you can use the Avoid obstructions option to specify that connectors do not intersect model elements. However, when you publish a model, the connectors might intersect model elements. To work around this issue, select the connector(s), clear the Avoid obstructions option, and manually adjust the bendpoints to avoid any obstructions. The next time you publish the model, the connectors will display correctly.

1.5 Icons in titles of model elements do not print properly

Icons in the titles of model elements, such as classes and packages, print with a white border. The white borders stand out against the titles, which print with a gradient shading. To print models without a gradient shading, turn off the gradient preference.

To turn off the gradient preference:

  1. Click Windows > Preferences.
  2. Expand Modeling and click Appearance.
  3. Under Global appearance, clear the Show gradient check box.

1.6 Dependency and realization connectors might not be visible in printed models

Dependency and realization connectors might not be visible in printed models. To work around this issue, change the line color of the connectors.

To change the line color of the connectors:

  1. Right-click the model; then click Select > All Connectors.
  2. From the toolbar, click the Line Color drop-down menu and select a darker color.

1.7 Cannot visualize non-composite properties in composite structure diagrams

Composite structure diagrams that are owned by a class can only contain properties that have their UML Aggregation property set to composite. These properties can be visualized. To visualize properties that do not have UML Aggregation set to composite, you must set the canonical behavior of the compartment to false. You can then visualize the non-composite properties by dragging them from the Model Explorer view onto the composite structure diagram.

To set the canonical behavior of a property:

  1. Select the background of the compartment.
  2. In the Properties view, click Advanced.
  3. Expand Styles and set the Canonical property to false.

1.8 Copying and pasting from the file system might corrupt models

You should not copy and paste models directly from the file system. Doing so can corrupt models, when you work with an original and a copy in the same workspace. Issues might also arise when you compare or merge a model, because of identical model element IDs. To work around this issue, use the Export as template option, or manually copy and paste the root elements into a new blank model.

1.9 Cannot easily add parameters or return types for behaviors

There is no easy way to add parameters or return types to behaviors.

To add parameters or return types to behaviors:

  1. In the Model Explorer view, right-click the behavior; then click Properties.
  2. In the list of properties, click Parameter.
  3. In the drop-down list, click Parameter or Result Type.

1.10 Properties might not update immediately on the Properties page

If you rename a diagram in the Model Explorer view, the name might not update immediately on the Properties page, under General. To work around this issue, select another diagram element in the Model Explorer view. The diagram information updates when you return focus to the diagram.

1.11 The Model Explorer view might not display stereotype names

If you apply multiple stereotypes to a model element, and one or more of the stereotypes has an icon, only one of the stereotype icons is displayed in the Model Explorer view. To work around this issue, set the stereotype style to text only.

To set the stereotype style to text only:

  1. Click Window > Preferences.
  2. Expand Modeling and click Views.
  3. On the Views page, set the stereotype style to Text.
  4. Click Apply.
  5. Click OK.

1.12 Cannot add stereotypes to multiple elements at one time

You cannot add stereotypes to multiple elements at one time. Doing so only applies the stereotype to the first selected element. To work around this issue, apply stereotypes to one element at a time.

1.13 Classes might not appear as cross-model references

When you move a diagram from one model to another, classes are not shown as cross-model references. To work around this issue, close and open the diagram. This refreshes the cross-model reference decorators.

1.14 Model connections might not update properly in the diagram editor

When you move a connection in the Model Explorer view, the diagram editor might not update properly. To work around this issue, delete the connection from the diagram editor and use the Show/Hide Relationships option to display the connection.

To show and hide connectors in a modeling diagram:

  1. In the diagram editor, right-click a diagram element; then click Filters > Show/Hide Relationships.
  2. In the Show/Hide Relationships window, click the relationships that you want to show, hide, or leave as is in the diagram, and click OK.

1.15 Show related elements option is not available for state elements

When you work with certain diagram types, such as activity, state machine, and sequence diagrams, the Show Related Elements option might not be available for state elements.

1.16 The Model Explorer view might not properly indicate unsaved changes

If you change a model file, close the UML Model Editor, and click No in the Save Resource window, the Model Explorer view indicates that the model file contains unsaved changes. The model file does not contain unsaved changes. The next time that you open the model file, the Model Explorer view displays the correct information.

1.17 Certain menu items do not appear on the Add UML pop-up menu

When you select a collaboration or use case in the Model Explorer view, certain menu items (for example, Interaction, Activity, and State Machine) do not appear in the Add UML pop-up menu. To work around this issue, use the Add Diagram pop-up menu to add the required behavior to the model file.

1.18 Default information in the Inheritance Explorer view is misleading

When you open the Inheritance Explorer view using the Window > Show View > Inheritance Explorer command, the information displayed in the Inheritance Explorer view is misleading.

To display the inheritance hierarchy of an element in the Inheritance Explorer view:

  1. In the Model Explorer view or the diagram editor, select an element.
  2. Right-click the selection; then click Navigate > Show in > Inheritance Explorer.

Alternatively, you can drag a model element from the Model Explorer view directly into the Inheritance Explorer view.

1.19 The product might display validation error messages that are not descriptive or useful

When you perform any of the following actions, the product might display a validation error message that is not descriptive or useful:

Return to the main readme file