Rational Rose for UNIX/Linux
Rational Rose, the world's leading visual modeling tool, allows you to define and communicate a software architecture, resulting in accelerated development, improved quality, and increased visibility and predictability.
The Rational Rose portion of the release notes describes new features and enhancements, known problems and limitations, and fixed defects since the last release. You will also find the Rose Extensibility Interface information in this section.
New Rational Rose Features and Enhancements
This release of Rational Rose includes these new features and enhancements:
Note: New and changed Rose add-in features are covered under separate add-in sections of this Release Note.
Rose.ini file replaced by rose.reg (Rose 2001a and after)
Any settings previously in the Rose.ini file are now in the registry file, rose.reg. This new registry file is located in the rational_dir/releases/rose.I.J.K/registry directory of the release. The settings in this file are entered in your registry, after running "rose_cleanup" and then "rose". Any changes made to the release rose.reg file will apply to all users running rose. If you wish to make changes specific for your environment, a rose.reg.template file is available in rational_dir/releases/rose.I.J.K/registry. Copy this file to your $HOME directory and name it $USER.reg. Edit this file with the settings you prefer, run rose_cleanup and then rose. Rose will automatically register your $HOME/$USER.reg file and your settings will be available in your Rose session.
Known Core Rose and Extensibility Problems and Limitations
The following table contains known Rose problems and limitations.
Defect
|
Description
|
1719
16674
|
F1 Help for keywords does not work in the Script Editor. Use the online Help table of contents or index to find the help you require.
|
1859
|
Fonts change when sharing units with team members using different default fonts.
Default font settings are currently stored with the model, and not with the .cat files. Items will only store font settings in a .cat file if the font is different from the default. As a result, text for model elements in units will be formatted, by default, according to the settings of the model. If one team member formats diagrams relying on a specific default color and font, that formatting will not be rendered for other team members with different default settings.
Workaround: Explicitly format text using a font that is different than the default setting.
|
1977
|
A business actor loses (changes) its fill color if it is moved around in the browser.
For example, change the fill color of the business actor from yellow to green and then move the business actor to a different package.
|
1981
|
Report > Show Usage does not work correctly.
|
1998
|
Problems dragging association point on a diagram.
|
2090
|
Print Preview does not work reliably for all diagram types.
|
2101
|
Print Specifications omits classes from the output report, without apparent reason or pattern.
|
2242
|
Drag and Drop of multiple selection from browser not supported.
The browser can be used to select multiple items, and the context menu can be used for that selection, but drag and drop of multiple items from the browser to a diagram is not supported.
|
2746
|
Rose hangs when checking out a controlled unit named with a special character.
|
3057
|
If you change the font size (through Tools > Options > Diagram tab) of a model element that is already on a diagram, the model element may not correctly resize. This happens frequently on activity and sequence diagrams.
Workaround - You can clean up the diagram using the Edit > Refresh command.
|
3078
|
Rose is inconsistent in how it handles user attempts to overload element names in different contexts.
|
3093
|
It is not possible to drag the "History" icon from the browser to the diagram.
|
3728
|
CDE window menu options do not appear when clicking in the top left hand corner menu of Rose.
Workaround: Minimize Rose and right click on the icon. CDE options, such as "Occupy Workspace" will then appear.
|
3861
|
Scroll bar in Language Properties dialog box may disappear.
Workaround: If this occurs, clicking in the scroll bar area will cause the scroll bar to reappear.
|
3877
|
Having a <return> character in the language properties Tools > Options "language tab" property fields can create a code generation problem. In addition, it is difficult to determine if a <return> character exists in language properties as it does not display.
|
3881
|
If a Java or Corba specification dialog is displayed and the Rose browser is not docked, Rose will lose focus when the specification dialog is closed. To proceed the user must terminate the Rose process and all unsaved data will be lost.
|
6397
|
CDE crash and technicolor affect when running on RDI Ultrabook if PGX graphics patch 105362-20 or higher installed. (May occur with previous PGX patches as well.)
|
6924
|
REI: RoseModel.FindItems() does not find attributes or operations.
|
7156
|
Encapsulated postscript file created by Rose which includes either multiple diagrams or diagram which exceeds one page size may print on one page creating distorted images.
|
7871
|
Text within the brackets on messages are lost on all sequence diagrams when the Apply button is clicked after changing the Message Signature option.
|
8718
|
The Fit to Page print feature will occasionally not leave enough space at the bottom of the page for the last element on a diagram. This happens when the diagram, as normally displayed, is just a little too large to fit on one page.
|
8845
|
The Test Dialog option in the Dialog Editor is not supported in this version of Rose for UNIX/Linux. Selecting the F5 shortcut key or the Test Dialog Icon will have no affect.
|
9168
|
Some custom stereotype icons added-in to previous versions of Rational Rose do not display correctly in Rose for UNIX/Linux.
|
9229
|
To change the ROSE_CPP path map variable, you must first manually remove its entry from the registry. In the Windows Registry, this pathmap variable is located at two different locations:
|
9535
|
Collaboration diagram numbering is thrown off by deleting and undeleting a link message.
Workaround: Turn Collaboration Numbering off and then on again to reset the numbering. (Select Tools > Options. Go to the Diagram tab and click Collaboration Numbering off. Click Apply. Click Collaboration Numbering back on and click Apply again.)
|
10388
|
Arial font size not consistent. Certain icons with Arial font style does not display the correct font size.
If 14pt Arial font size is selected, certain icons (i.e: usecase/business/interface) icons may display in 12pt size.
|
10622
|
Print output may not appear the same as the screen display.
This issue only occurs when printing from a UNIX/Linux display. This does not occur when printing from a PC display using Exceed.
|
11133
|
Fit/Undo Fit in Window may result in undesirable layout. Undo Fit in Window may not result to its original display/layout.
|
11416
|
Font scaling difficulties when using Rose fonts.
Problem with scaling occurs when doing print preview.
|
11615
|
Help button on title bar missing.
The ? button on the title bar of various dialogs (located left of the X button) does not appear initially, unless:
- 1 The area where the ? button should appear is clicked on.
- 2 The window area containing the spot where the ? button should appear is moved off screen, and then moved back on screen.
|
11800
|
You may encounter an unresolved model warning if there is a view of an item on a diagram, but the underlying item is not loaded or could not be found in the current model.
Items and relations are correctly displayed and reported by Check Model as unresolved references when the view to the item is in a diagram that is in the current model but the item resides in an unloaded package (controlled unit). The reference becomes resolved and the unresolved indicator is removed when the unit containing the item is loaded.The unresolved model warning occurs occasionally during model loading if the model was created by a previous version of Rose and that version of Rose allowed an invalid model to be created. Some known cases are:
Circular Generalize/Realize Relationship Combinations (allowable in Rose2000e but no longer valid in this release). Note that if you attempt to create a circular generalize/realize relationship combination, you will get an error and the relationship will not be created.Circular generalize/realize relationship combinations that exist in models files created with earlier versions of Rose are detected on model load and one of the relationships involved in the circularity is left unresolved.
You may delete the unresolved view and then add new ones as appropriate. Running Tools > Check Model will provide in a list of unresolved views in the Rose log. If the relationship has no view on a diagram in the model, then an "unresolved relation" warning is placed in the Rose log. The warning is also generated by Tools >Check Model.
To correct the unresolved relations:
- 1 Load the model into the Rose
- 2 Check the log file for "Unresolved relation" warnings
- 3 Open the spec of the "from" class to the relations tab
- 4 Note that the unresolved relation (generalize or realize) is the one with the class name in brackets in the name column
- 5 Determine which classes are involved in the circularity
- 6 Delete the undesired relationship via the class spec relations tab
Shared Objects - Shared activity diagram objects (allowable in Rose2000e but no longer valid in this release). A shared object is an object that belongs to one state machine and has a view on an activity diagram belonging to another state machine. The drag and drop of the object is now disabled if the object does not belong to the same state machine as the diagram.In general, the unresolved object can be deleted from the diagram and a new object can be created on that diagram. The model does not lose integrity or validity for doing this since an object is not actually a model item - it doesn't define anything, it is only an instance of a class used for visualizing state or behavior.
|
11810
|
Printed diagrams can differ from what is displayed on the user's screen. For example, some longer operations do not print completely.
If the text on the screen is:
provideWorkflowClosure(WorkItemClosureData) : void
the printout might only show:
provideWorkflowClosure(WorkItemClosureData) : v
|
11879
|
Display problem with Message\More dialog and long names.
|
14249
|
A new Creates a Form class diagram toolbar is available, but you must manually add it to the toolbar.
|
14739
|
If you use the inline-editing capability on a diagram to rename an operation parameter name, then any OVERRIDDEN model properties associated with that parameter are reset to the DEFAULT value.
Note that if you rename the RoseParameter via REI or through the specification dialogs, then the model properties are not reset.
|
15037
|
Role Name will not remain on diagram if context menu is used to create it.
Workaround: Define the Role Name using the Association Specification dialog.
|
17061
|
If a state or activity diagram contains a view of an element from another state or activity diagram/model, the Query > Expand command will not work for that element.
|
18168
|
Deleting a package with a class attached to a read-only object in an activity diagram will cause Rose to crash.
|
18229
|
Encapsulated Postscript %%Page and %%BoundingBox not conforming to standard.
|
18733
|
Infrequently, a modal dialog may move behind Rose. In this event, you will need to move Rose to access the modal dialog.
Contact Rational Technical Support if you encounter this issue. See Contacting Rational Technical Support.
|
18734
|
It is not possible to delete an unloaded controlled unit from a model. To delete a unit from a model, first load that unit and then delete it.
|
18890
|
Rose may crash when Web Publishing a model if the following environment variables are not set, *and* csh unlimit has been run, prior to running Rose:
|
25404
|
Some diagrams can lose or have additional vertical toolbars.
|
31538
|
On Solaris displays, double clicking on the top bar of the IEditor can cause the IEditor to disappear. This defect does not occur on other UNIX displays or on PC displays, running Exceed.
|
57200
|
'x' is disabled in the 'error Box' when drawing a 'Realize' reationship from 'class' to 'package'.
|
58064
|
IEditor Horizontal scroll bar may not appear.
Workaround - Bring up the IEditor by selecting View:Editor prior to browsing code. If the IEditor is already running, the horizontal scroll bar will always correctly appear.
|
66268
|
Context menu arrow may not display properly when the class is placed at the edge of the window.
|
66926
|
Diagram items not dragging correctly after using 'birds eye view' utility.
|
Fixed Defects in Core Rose and Extensibility Version 2002.05.00
Defect
|
Description
|
1718
|
Add "use qualified name" to all "Add Relation" descriptions.
|
8972
|
REI - Diagram Class: Render, PrintPostScript now available on UNIX. RenderEnhanced will write to a file iff a valid file is provided through the interface. It will also determine the file type based on the extension and write a jpeg, tiff or postscript file as appropriate.
|
13700
|
Moving a state causes the transition labels to move incorrectly.
|
18462
|
Rose Class Wizard disabled when model file is write protected.
|
18698
|
Rose may crash when selecting a context menu from the Class diagram, after closing the Java Reverse Engineering dialog. This issue is under current investigation.
Contact Rational Technical Support if you encounter this issue. See Contacting Rational Technical Support.
|
25410
|
Editor status bar for "Ln" and "Col" may show incorrect text.
|
30165
|
When a message is created between two existing messages and the sequence numbering is on, the new number is drawn at the very bottom of the diagram.
Workaround: Manually reposition the message sequence number label.
|
30174
|
A black line may appear upon highlighting text, after code generation, in the Rose editor.
|
30316
|
Cannot add new custom stereotype text for an association.
|
30475
|
Only three files can be added with the Insert File command on Package Specifications.
|
30829
|
Calling IRoseStateMachine.DeleteStateDiagram may not delete StateCharts from StateMachines.
|
31026
|
During file save, Rose does not warn the user if there is not enough disk space to save the complete model.
|
31544
|
Can't use text note on dependencies between associations
|
31676
|
Aggregation association qualifiers can not be deleted from the diagram.
|
53487
|
In some cases, message that should be received by the primary focus of control on a sequence diagram were being directed to the secondary focus of control.
|
53542
|
Zoom 'Fit To Window' truncates operation name display in class.
|
54176
|
REI GetInstance crashes on new ClassInstanceView.
|
54183
|
REI ClassInstanceView identified as NoteView by InstaceView.IdentifyClass
|
54233
|
Method name not displayed on sequence diagram.
|
54295
|
Rose may crash when invalid path is added to the Virtual Pathmap.
|
54594
|
Unresolved reference when deleting package containing component that is the supplier of a dependency.
|
54828
|
Class icons cannot be resized when the Automatic Resize option is turned on in Rose 2001A.
|
54944
|
Rose 2001A crashes when deleting packages in the browser.
|
54986
|
On start up Rose is modifying user specified registry entries.
|
55054
|
Check Model reports error when Sequence diagram uses Destruction Marker.
|
55389
|
Older models that have message with return type on sequence diagram can cause Rose to crash.
|
55401
|
Diagram elements redraw themselves on top of each other when reloading using ClearCase.
|
55533
|
When copying packages, copied associations may have the wrong ID.
|
55731
|
Layout diagram crashes Rose when the diagram has missing associations.
|
55803
|
Rose will crash when trying to edit sequence diagram that is located in a read only package.
|
55987
|
If an activity's name is too long to fit on a single line, after editing the name, only the second line of the name is displayed on the diagram.
|
56043
|
Non-default properties can be lost, upon loading model.
|
56222
|
AutoConstructMainDiagrams doesn't work correctly for diagrams in unloaded units.
|
56242
|
Property values added to a Rose model can be lost when the model is reloaded.
|
56418
|
Enabling three-tiered diagrams option removes the Creating UseCase diagram option in the shortcut menu under Logical View package and subpackages.
|
56429
|
Apply doesn't update the Stereotypes for attributes.
|
56990
|
REI: Activity.GetObjectFlows() only returns outgoing object flows.
|
57039
|
After renaming a formal parameter to a parameterized class, when an attempt to delete the parameter was made an error message was displayed.
|
57121
|
Eliminates clipboard conflicts with SoDA by writing graphics files directly to the file system. Support for encapsulated postscript files is added as a generation option when using the SoDA-Rose integration. To generate postscript graphics, set SODA_GRAPHIC_FORMAT to eps prior to starting SoDA.
|
57241
|
When doing a deep delete of a message in a sequence diagram Rose may crash.
|
57331
|
Attaching a note to a destruction marker in sequence diagram can cause Rose to create a corrupted model.
|
57615
|
"File" menu could disappear while in Use Case view, after running 'rose_cleanup'.
|
57761
|
Message labels are reformatted when a model is reloaded.
|
57859
|
Resizing Role name/specifier text box causes role name/specifier to not always be displayed.
|
57954
|
Moving messages on sequence diagrams may result in Rose redirecting message incorrectly.
|
58031
|
Footer is not included on the printed margin until the bottom margin is increased.
|
58035
|
Values entered in specification dialogs are lost when switching between the dialog tabs.
|
58157
|
Displaying some custom stereotypes for activities as icons can cause Rose to crash.
|
58480
|
Opening diagrams and specification dialogs can be slow on large models.
|
58660
|
Fully qualified names for types in operation return and argument types are not updated when the class is relocated.
|
58717
|
Qualifier disappears when you double click in the label box.
|
58746
|
Erroneous unresolved relation and Invalid circular Inheritance errors may be reported.
|
58867
|
The state transitions can become corrupt when relocating activities.
|
59045
|
Model created in Rose 2001A with sequence diagram messages to self can cause Rose to crash.
|
59160
|
Statechart Transition Text does not maintain location when the model is reloaded.
|
59892
|
Rose crashes when trying to delete a class from a read only class diagram.
|
60019
|
Message signature corrupted in write protected sequence diagram.
|
60195
|
In nested activity models object state is not displayed.
|
60306
|
Extra white space may appear in print output at the end of class box / compartment.
|
60850
|
If a user zooms out on a Activity diagram, modifies the activity text and then zooms back in, the text will be displayed incorrectly.
|
58937 & 62316
|
Random Rose crash can occur, producing stack traces which may begin with the following:
-MwIDefWindowProc
-MwICreateFontIndirect
-MwICreatePenIndirect
-MwICreateBitmapIndirect
Related to the availability of font handles.
|
Rose Extensibility Interface (REI) Release Notes
Rose Extensibility Interface Features and Enhancements
The Rational Rose Extensibility Interface (REI) provides several ways for you to extend and customize Rose's capabilities to meet your specific software development needs. Using REI capabilities, you can:
There are no new features or enhancements for this release of the Rose Extensibility Interface (REI).
Netscape V4.7x Issues
Netscape 4.7x is provided in the rational_dir/base/cots/netscape.4.7x/$arch directory of this Release. rs_help uses Netscape to display Installation Guide and Release Note information. Rose for UNIX/Linux will occasionally use a browser. Rose will first use the browser defined in the users "BROWSER_PATH" environment variable or Netscape included in this release, if BROWSER_PATH is not defined.
If you have not used Netscape 4.7x, we recommend you consult the Netscape README file located at
rational_dir/base/cots/netscape.4.7x/$arch/README
This file includes a warning, recommending that an existing $HOME/.netscape file or directory be renamed prior to running Netscape 4.7. Otherwise, data may be lost (i.e. old preferences, bookmarks, cookies, etc.). The README file includes other helpful information such as platform specific issues as well.
