Rational Rose Release Notes

Version 2002.05.00
Windows
Part Number: 800-025350-000


Scope

These Rational Rose release notes provide:

The printed and electronic versions of the release notes that were packaged with your software contain the most up-to-date information available at release time.

Updated versions of the release notes will periodically be posted on the World Wide Web. Please check the Rational Web site at http://www.rational.com/support/documentation/release/ to ensure that you are using the latest version of this document.

When you are ready to install Rational Rose, be sure to check the Web for the latest available downloads:

1 . From http://www.rational.com, click Support.

2 . Go to the Download Center and navigate to Rational Rose Upgrades and Patches.

Also remember to have the Installing Rose and Administering Licenses manuals available to provide all the information you need to complete your installation.


Trademarks and Copyrights

A complete online trademark and copyright information page for all Rational products resides in the /doc subfolder of your installation folder. The file is called copyright.html, and its default location is C:/Program Files/Rational/doc.


Product Definition

Rational Rose helps customers design and develop software in an Internet-connected, global economy. As the Internet has grown to dominate both business and technology decisions, all organizations face an e-software paradox. Traditionally, development organizations could choose between higher software quality or reduced time-to-market. In the new Internet economy, organizations have no choice: they must deliver higher quality software in less time. Rational Rose helps companies overcome the e-software paradox by unifying the communities that develop software with a common visual language that accelerates the creation of flexible applications with robust, resilient architectures.


System and Software Requirements

This section describes the system and software requirements for installing and running Rational Rose and its add-ins.

Server System Requirements

To plan your Rational Rose environment, you will need to determine which systems, if any, will be server machines. Server systems need to be highly available, and may need extra memory and disk space. The following table describes the types of servers you may need.

Table 1 Servers Used with Rational Rose
Type of Server

Description

License server
If you use floating licenses, you need to set up a server to administer the licenses. For more information, see Administering Licenses for Rational Software.
Database server

Additional System and Software Requirements

The following table describes the additional system and software requirements for Rational Rose and its add-ins.

Table 2 Rational Rose Requirements 
Item

Minimum Requirements

Operating Systems

Hardware Requirements

Windows Terminal Server Client
Rose supports Windows Terminal Server Client on these platforms:
Hosted Development Systems (remote sessions)
Rose supports hosted development on these platforms:
Web Browsers
Rose add-ins that use a Web browser (for example, Web Publisher) support most common browsers. Note: Because some Rational products require certain Microsoft Internet Explorer components, if the Rational Setup program does not detect Internet Explorer 4.01 on your system, it will not allow the installation to proceed. This does not mean that you are required to use Internet Explorer as your browser. If you do not have Internet Explorer, you can download it from Microsoft's Web site: http://www.microsoft.com/windows/ie.
Web Clients on Non-Windows Platforms
Rose supports Netscape 4.x on Solaris 2.51 or later, or on HP-UX 10.20 or later
Microsoft JVM
MS JVM Build 3802
Java
Rose J supports the following Java IDEs. Use the JDK appropriate to your IDE.
Network Server Requirements
If you use Sybase SQL Anywhere software, make sure that your database server meets the following minimum hardware and software requirements:

Note: Novell NetWare is no longer supported for network servers.


Rose Data Modeler Databases

Rose VC++
Requires Microsoft Visual C++ 6.0 (Visual Studio 6.0)
Rose Visual Basic
Requires Microsoft Visual Basic 6.0 (Visual Studio 6.0)
Rose J
Requires JDK 1.1.6
Monitor
SVGA-compatible display (256 or more colors recommended) with resolution of at least 1024 X 768 pixels
Mouse/Pointing Device
Any pointing device with at least two buttons
Automated License Key Requests
Internet connection required for license requests
Dual Boot Systems
Installation of Rational Rose on dual-boot systems is not supported
Archive Utility
WinZip or equivalent
Rational Documentation
Adobe Acrobat Reader 4.x or higher to read online PDF files


Rose Documentation

The goal of all Rose technical documentation is to provide the most appropriate and usable product information possible so that our users can benefit fully from all of the features of Rose and its add-ins. To that end, Rose and its add-ins provide a complete, integrated online Help system, along with a set of supplemental printed manuals.

Rational Rose printed documentation and some online Help has not been updated for this release. Updates were, however, made to the Rose J and the Rose ANDI C++ online Help systems. Please note that you can still order the previous version of printed documentation, most of which remains valid for this release. It is recommended that you are aware of any important changes to functionality or behavior.

Online and Printed Documentation

You may have noticed that the printed documentation set has changed recently. Several printed manuals have been eliminated because their content was exactly the same as that of the online Help. On the other hand, several newer books that provide important background or supplemental information are now available. In future releases, we hope to provide more of these value-added publications, while continuing to update our comprehensive online Help systems.

To print the complete online Help for Rose or any of its add-ins, you can easily do so from the Contents tab of the Help system:

1 . On the Rose Help menu, click Contents and Index.

2 . On the Contents tab, click the help book that contains the help you want to print.
(For example, to choose the entire help for Rational Rose, click the Rational Rose help book; to choose the entire help for Rose J, click the book called Rose J.)

3 . Click Print.

All of the Help topics contained in the selected book (including those that are contained in sub-books of the selected Help book) will print in the order in which they appear in the table of contents.

Of course, you can still print single topics whenever you need to do so.

In addition to the Release Notes, the following manuals constitute the printed documentation available for Rose and its add-ins:

These manuals are also available in Portable Document Format (PDF) on the documentation CD that comes with all editions of Rational Rose. You can also download the PDF files from the Rational Web site, http://www.rational.com.

Rose Tutorials

Tutorials that Come with Rose

The documentation CD contains a comprehensive online tutorial for Rose, as well as one for the Rose Oracle8 add-in. You can also access Rose tutorials on the web by going to http://www.rational.com and navigating to the Try It Center for Rational Rose.

The Rose tutorial is distributed as a self-extracting archive file that is meant to be copied onto the hard drive of the machine where Rose is installed. The file is approximately 4MB in size and its name is RoseTutorialFiles.exe. When extracted, it requires approximately 28MB of free disk space. For more information, refer to the Tutorial Read Me file, which is accessible from the Rose Start menu.

Note: Even though the name of the Rose tutorial has not changed (it is still called Rose 2000 Tutorial), several errors from previous releases have been fixed.

The Rose tutorial provides an overview of Rational Rose, and then takes you through the application development process beginning with business modeling all the way through application implementation, with detours into data modeling and team development.

Tutorial Guidelines

The self-extracting file that contains the tutorial does not uninstall when you uninstall Rose from your system. You must manually remove the tutorial files when you uninstall Rose.

For best tutorial viewing quality, set your display's Color Palette to True Color or to the highest number of colors possible.

Note: In Windows, you can control your display settings from the Control Panel.


Contacting Rational Technical Support

If you have questions about installing, using, or maintaining this product, contact Rational Technical Support:

Your Location

Telephone

Fax

E-mail

North America
(800) 433-5444 (toll free) (408) 863-4000 Cupertino, CA
(781) 676-2460 Lexington, MA
support@rational.com
Europe, Middle East, Africa
+31 (0) 20-4546-202 Netherlands
+31 (0) 20-4545-201 Netherlands
support@europe.rational.com
Asia Pacific
+61-2-9419-0111 Australia
+61-2-9419-0123 Australia
support@apac.rational.com

When you contact Rational Technical Support, please provide the following information:


Getting Started

Consider the following guidelines as you plan to install or remove this version of Rational Rose.

Rose Add-in Guidelines

If you are using any supported Java IDE, be sure to install it before you install Rational Rose. If your Java IDE is not installed before Rose, the Rational Setup program will not install the correct Rose add-in.

General Guidelines

Licensing and Permissions Guidelines

File Location Guidelines

Shared File Guidelines

The Rational Software Setup program installs some shared components, which are potentially available to other applications on your system. Setup installs the U.S. English version of these files. It does not overwrite newer file versions.

If the Setup program needs to update shared components, it displays a list of the shared components that require updates. The files listed must be installed on your system before the installation can proceed.

In general, we recommend that you allow the installation procedure to install shared files for you. In the following circumstances, you may want to install the files yourself:

Backup Guidelines

You should back up your registry and system directories prior to running the Rational Software Setup program. In addition, make system backups of any machines on which you plan to install Rose. Specifically, we recommend you make backups of the following files:

Version Compatibility Guidelines

If you have older Rational products installed on your system, you must ensure that all Rational products on that system are upgraded to the same version. Because Rational tools share files and components, a new installation can cause the older Rational products to stop working. You will see no visual clue that the older products may be compromised.

See the Installing Rose manual for complete information.


Core Rose and Rose Extensibility Interface

Core Rose Features and Enhancements

This release of Rational Rose includes these new features and enhancements:

Core Rose and Extensibility Defects Fixed in This Release

Defect

Description

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.
57039
After renaming a formal parameter to a parameterized class, when an attempt to delete the parameter was made an error message was displayed.
57241
When doing a deep delete of a message in a sequence diagram it crashes Rose
55401
Diagram elements redraw themselves on top of each other when reloading using ClearCase
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.
56242
Property values added to a Rose model can be lost when the model is reloaded.
54828
Class icons cannot be resized when the Automatic Resize option is turned on in Rose 2001A
53858
On German operating systems, when dragging activities from the browser to an activity diagram in another state/activity model, you often get circle M (not in model) after reloading the model.
13700
Moving a state causes the transition labels to move incorrectly.
58157
Displaying some custom stereotypes for activities as icons can cause Rose to crash
57331
Attaching a note to a destruction marker in sequence diagram can cause Rose to create a corrupted model.
59160
Statechart Transition Text does not maintain location when the model is reloaded.
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.
59045
Model created in Rose 2001A with sequence diagram messages to self can cause Rose to crash.
58746
Erroneous unresolved relation and Invalid circular Inheritance errors may be reported.
58035
Values entered in specification dialogs are lost when switching between the dialog tabs.
57954
Moving messages on sequence diagrams may result in Rose redirecting message incorrectly.
55533
When copying packages, copied associations may have the wrong ID.
55389
Older models that have message with return type on sequence diagram can cause Rose to crash.
56990
REI: Activity.GetObjectFlows() only returns outgoing object flows
56047
File : "Save subunits of <...>" doesn't work on win NT
56429
Apply doesn't update the Stereotypes for attributes
54183
REI ClassInstanceView identified as NoteView by InstaceView.IdentifyClass
54233
Method name not displayed on sequence diagram
54176
REI GetInstance crashes on new ClassInstanceView
54594
Unresolved reference when deleting package containing component that is the supplier of a dependency
31676
Aggregation association qualifiers can not be deleted from the diagram
31544
Can't use text note on dependencies between associations
53542
Zoom 'Fit To Window' truncates operation name display in class
54986
On start up Rose is modifying user specified registry entries.
55054
Check Model reports error when Sequence diagram uses Destruction Marker.
54944
Rose 2001A crashes when deleting packages in the browser
31026
During file save, Rose does not warn the user if there is not enough disk space to save the complete model.
30829
Calling IRoseStateMachine.DeleteStateDiagram may not delete StateCharts from StateMachines
30475
Only three files can be added with the Insert File command on Package Specifications.
30316
Cannot add new custom stereotype text for an association.
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.
58031
Footer is not included on the printed margin until the bottom margin is increased.
58717
Qualifier disappears when you double click in the label box.
58867
The state transitions can become corrupt when relocating activities.
59892
Rose crashes when trying to delete a class from a read only class diagram
60019
Message signature corrupted in write protected sequence diagram.
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.
60195
In nested activity models object state is not displayed.
60306
Extra white space at the end of the class box/compartment in the print output
56418
Enabling three-tiered diagrams option removes the Creating UseCase diagram option in the shortcut menu under Logical View package and subpackages.
56222
AutoConstructMainDiagrams doesn't work correctly for diagrams in unloaded units.
18462
Rose Class Wizard disabled when model file is write protected

Known Core Rose and Extensibility Defects

Defect

Description

no number available
The Help topic Visual Studio RTE Extensibility Drag-Drop Add-In Sample, section How to Run the Sample requires the following update:
1575
When starting Rose, sometimes the introductory splash screen takes over the entire screen and you cannot do anything else until Rose is loaded. Workaround: Use the - noSplashScreen command line switch to control display of the splash screen. Use one of the following methods to set this switch: 1. In Windows, click Start > Run. 2. At the command prompt, enter rose.exe -noSplashScreen. Alternatively: 1. Start Rose from an MSDOS command line prompt by entering the following command: start rose.exe -noSplashScreen
1934
Korean character input; slow display for question marks. If a class name contains a question mark (?), Rose takes longer than expected to display the class name. Turning autosize off will help alleviate the delay.
2090
Print Preview does not work consistently for all diagram types.
3093
The Activity icon does not display the history graphical depiction on it. It is also not possible to drag the "History" icon from the browser to the diagram.
7871
Text within the brackets on messages is lost on all sequence diagrams when user clicks Apply 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
9168
Some custom stereotype icons added to previous versions of Rational Rose do not display correctly. Workaround: Open the icon file (.wmf) in a graphics application that supports .wmf files. Set the color palette to Transparency.
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:
11555
Problems with McAfee Virus Scan software When some software is installed or launched, some virus scanners check each file, including .dll and .ini files, being read and loaded, as part of their normal process. However, this functionality can significantly increase the amount of time it takes for some software to load. This is a result of the interaction between the loading software's dynamic extensibility functionality and the virus checking mechanism used by the anti-virus software. This functionality of certain anti-virus software could affect the performance of Rational Rose and of the Rational Installer. Rose stores a significant amount of information in the default stereotype.ini file, as well as ini files used by different Rose Add-ins. Rose accesses keys in these ini files using the standard windows calls, which unfortunately open, search, and close the ini file every time we query for a key from a file. This means that McAfee scans the complete ini file every time we attempt to read a key, literally 100s of times for some of the files. This, in addition to the dll scanning that is exacerbated by the fact that Rose' is comprised of many components, is the cause of the slowdown in Rose startup. The best solution at this time is to disable scanning of ini files in McAfee. To do this follow these steps:

1 . Go to the system tray and double-click the Vshield icon.

2 . In the System Scan dialog, click Properties.

3 . In the Properties dialog, make sure that the Virus scanner is scanning for program files only.

4 . Click Extensions.

5 . In the Program File Extensions dialog, find the .ini extension and click Delete .

6 . Click Ok to close the Program File Extensions dialog.

7. In the Properties dialog, click Apply to save the changes.

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 the Check Model command 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 using 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 ). 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 upon 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 RoseLog. The warning is also generated by Tools->Check Model. To correct the unresolved relations:

1 . Load the model into Rose.

2 . Check the Log file for Unresolved Relation warnings.

3 . Open the Class Specification for the client class and click 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 using the Class Specifications Relations tab.

Shared Objects - Shared activity diagram objects (allowed 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 because of this since an object is not actually a model element -- it does not define anything, and 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
14249
A new Creates a Form class diagram toolbar is available, but you must manually add it to the toolbar.
16544
Module 6 of the tutorial asks you to register some DLLs. These are the DLLs that are shipped with the tutorial. Doing this on Windows 2000 may fail, causing an error when attempting to drag the DLLs to the regsvr32.exe. You may need to give yourself administrative rights to your machine in order to complete this step in the tutorial.
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
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.


Rose C++ Add-In's

Rose ANSI C++ Add-In

Rose ANSI C++ Enhancements Added in This Release

Please note that the ANSI C++ and VC++ addins are the only supported C++ addins in Rose. We are no longer supporting the Classic Rose C++ addin.

Rose ANSI C++ provides:

Rose ANSI C++ Defects Fixed in This Release

Defect

Description

31579
Return type generated for Constructor if added with "class customization"
55273
If the complete model is not selected, the model converter may crash
55676
Const not showing up in the generated ANSI C++ code
56139
ANSI C++ Converter removes inheritance relations from model
30463
Duplicate ModelIDs generated for typedef in Ansi C++
25468
Parametrized class documentation lost from the model after reverse engineering
23123
Class customization: Attribute get and set methods with qualified type names
23370
ANSI C++ Converter does not preserve model documentation
54367
Converter error: Parameterized class to be instantiated not defined
54723
Invalid ANSI C++ code generated when class stereotype changed from "struct" or "enum" to a user stereotype
25046
ANSI C++ Tab missing on component with part=Body or part=Main
62314
An enum is first reversed as attribute and then as association

Known Rose ANSI C++ Defects

Defect

Description

55269
OperationIsConst property not converted to ANSI C++ as stereotype for operation
55272
OperationKind C++ property not converted to ANSI C++ stereotypes
56256
Inline property of operation lost while converting from Classic C++ to ANSI C++
56258
OperaionIsExplicit property not converted to ANSI C++ as stereotype for constructor
30368
Code generation error in ANSI C++ where a type has $ sign in its name
55134
Codename property not saved when converting from Classic C++

Rose C++ Add-In

Rose C++ Features and Enhancements

Note: This addin is no longer supported. The addin is still shipped with Rose but is disabled by default. If the addin is needed, it can be enabled using the addin manager available from the Rose top level menu.

Rose Visual C++ Add-In

Rose Visual C++ Features and Enhancements

The Rational Rose Visual C++ Add-In provides the interface between the Rational Rose modeling environment and Microsoft Visual C++. The main features of Rational Rose Visual C++ include:

Upgrading from Rose 2000 Visual C++ Add-In Release

This release of the Rose Visual C++ Add-In is backward compatible with previous versions of the add-in.

The support for MIDL in this version of Rose is deeper than in previous versions of Rose. When you use the Code Update Tool or Model Update Tool on a model created by Rose 2000, this version of Rose will automatically add new components stereotyped as <<MIDL>> for existing components that represent MIDL projects. Model classes that are stereotyped <<coclass>> or <<interface>> will automatically be assigned to the <<MIDL>> components.

It is recommended that you use the Model UpdateTool on any Rose 2000 models before attempting to generate code using this version of Rose.

Converting Models from Rose Classic C++ to Rose Visual C++

The model formats used by the Visual C++ and Classic C++ Add-Ins are not interchangeable. If you want to use the Rose Visual C++ on models created for use with Rose Classic C++, you must convert the models using the Model Converter.

To do this, on the Tools menu, click Visual C++ > Model Converter.

Rose Visual C++ Defects Fixed in This Release

Defect

Description

30956
In order for model update to work, the affected component packages need to be write enabled
23313
Can not use a wildcard when creating VC++ ProjectFolders property
16540
VC MUT needs better error messages for Model Update Tool
56430
In the Model Assistant tool, the implementation field gets focus when you first type
56658
VC++ code is not updated correctly after changing return type
54215
Rose VC++ generates wrong code if "::" is used in the parameter fields for an operation
30963
CG of conversion operator doesn't work with namespace
30892
Wrong update of code in VC++ AddIn for classes with separated header and source files
53814
Incorrect initialiser generated in VC++ Addin
24886
Bad code generated for methods when changing arguments order
57326
Methods body defined in templates are not generated
60659
VC++: Rose crashes if you uncheck the derived operation
57775
VC++ RE fails for method with parameter of CArray type
55807
VC++ generalization relationships that are deleted from a model do not get deleted in the generated code
31023
Include Statement does not use the HeaderFileName and CodeFileName properties
21093
Update Code causes duplicated files in VC++ with some component stereotypes
57327
Command Range Handlers will cause Rose to generate the wrong code
61578
Add Method dialog for ATL objects duplicates the methods in the ATL object.
21771
VC++ code generation HeaderFileName Class Property inconsistent behaviour

Known Rose Visual C++ Defects

Defect

Description

15940
 If you generate code for a function named Test1() that is stereotyped as <<abstract>>, and has no return value, the code generated will be: virtual Test1() = 0; If you now add a return type in the model and generate code again, the new return type will not be generated in the code. Workaround: Manually add the return type in the code. The Model Update Tool can be used to update the model with the new return type. When both the model and code have a non-null return type, the Code Update Tool will correctly generate changes in the model's return type into the code.
15946
If you generate code for a class that has an initial value for a non-static class attribute, the initialization code will be generated in the default constructor. However, if you rename that attribute and generate code, the old initializer will remain, and a new one for the renamed attribute will be added. Workaround: Remove the old initializer.
15977
The Synchronize tab on the Model Update Tool and Code Update Tool displays nested classes as separate check box items. If you select a nested class, then that class will be deleted. However, deleting an outer class will also delete any nested classes that are contained within that class, even if the nested classes are not selected.
01389
Model Assistant should not show parameterized classes as override class
01375
Quick import in Model Assistant may not show all imported information until the window is closed and reopened


Rose Ada Add-In

The Rose Ada add-in allows you to produce Ada source code from the information contained in a Rose model.

The code generated for each selected model component is a function of that component's Specification and code generation properties, and the model's properties. These properties provide the language-specific information required to map your model to Ada code.

Rose Ada preserves user-supplied declarations and statements from one iteration to the next. You place such user-supplied code in protected code regions which are preserved whenever code is regenerated.

The Rose Ada code generator:

New Rose Ada Features and Enhancements

There are no new Rose Ada features for this release.

Rose Ada Problems and Limitations

The following list describes the known problems and limitations for this release of Rose Ada:


Rose ClearCase Add-In

Rose ClearCase Features and Enhancements

The ClearCase add-in provides a tight integration between Rational Rose and the Rational ClearCase version control system. This add-in is intended to replace the ClearCase capabilities provided through the generic Version Control Add-In. Unlike the Version Control Add-In, the ClearCase Add-In does not use the Microsoft SCC API to communicate with ClearCase. This allows for more ClearCase-specific customization.

If you are already familiar with the Version Control Add-In, you will find the transition to the ClearCase add-in simple because many of the dialogs and menu items are identical.

Rose ClearCase Addin Defects Fixed in this Release

Defect

Description

9587
Have to reload subunits after "undo check out" in ClearCase
21316
Rose crashes if Source Control provider loses connection to Rose

Known Rose ClearCase Addin Defects

Defect

Description

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.


Rose 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:

Rose CORBA Defects Fixed in This Release

Defect

Description

55732
Recursive association on Corba valuetype is not code generated
56145
CORBA IDL forward interface declaration not generated
60418
Additional includes does not generate to code.
24861
Parser errors during Corba reverse engineering because include files in wrong order
58381
Parser errors when trying to reverse engineer IDL file

Known Rose CORBA Defects

The Rose CORBA online Help references the old Rose internal editor (R2Editor); however, Rose CORBA now uses the new internal Rose editor.


Rose Data Modeler Add-In

Rose Data Modeler Features and Enhancements

Rational Rose Data Modeler is a database modeling and design tool that usesUML (Unified Modeling Language) notation. It allows you to work with UML object models as logical models and data models as physical models, and helps you maintain synchronization between the data model and the database.

Data Modeler supports round-trip engineering between the data model, the object model, and the database or DDL file. You can:

In addition to round-trip engineering, you can build a data model. You can:

The following information describes the new features that are available for this release of Rose Data Modeler.

Databases

Data Modeler now supports Microsoft SQL Server 2000, including the following SQL Server 2000 features:

Data Model Elements and Specifications

Data Modeler allows you to create, edit, delete, and use Specifications for the following new elements:

Data Storage Modeling

Data Modeler now supports data storage modeling for DB2, Oracle, and SQL Server. You can:

You can also assign tables to a tablespace using the enhanced Table Specification.

Modeling Views

Data Modeler now supports modeling views in a data model. You can:

Rose Data Modeler Defects Fixed in This Release

Defect

Description

54920
Sybase Stored Procedures are not being reversed engineered.
62685
java.lang.NullPointer Exceptions appearing when Comparing and Syncing model with database
54219
Language default changed unexpectedly
29183
Data modeler This functionality Delete,Relationship is not currently supported
57794
Rose fails to RE DDL script files using MS SL 2000

Known Rose Data Modeler Defects

Defect

Description

55176
SQL Server Stored Procedure parse error @ macro /* comments
66308
Not Null values not holding on Columns


Rose Framework Wizard

Rose Framework Wizard Features and Enhancements

The Framework Add-In provides a library of frameworks that can be used as templates when creating new models. The Framework Add-In also provides a wizard that helps you add additional frameworks.


Rose J Add-In

General Features and Enhancements

The Rose J add-in supports true roundtrip engineering and provides support for large frameworks. This release of the Rose J add-in provides the following new capabilities:

Rose J and J2EE Defects Fixed in This Release

Defect

Description

55563
Javadoc comments generated for J2EE code that I cannot turn off!
55440
SetSessionContext method get duplicated at code generation time when using the J2EE framework
56054
J2EE and RE of EJB with inheritence
56167
Added new EJB method goes to a different Bean component than the one selected.
54566
Add and Repair EJB leave wrong dependency.
57564
Method bodies are lost after regeneration of code
55432
EJB created after loading J2EE framework misses throws statements in model
56240
Check & Repair option problems
53787
redundant import statements
29530
Missing javadoc for simple property in j2ee
29181
equals method in Entity EJB PK missing Object parameter
57845
Rose and EJB create method error
55345
Java specification settings are not retained
55766
Java reverse engineering fails with parser error.
55802
Getters and setters set via Bean properties are not considered as inherited operations
56550
Class loses DocComments when RE Java files
56133
Java does not record paths to generated source files using virtual path map symbols
54359
Container class option for aggregation to nested classes generate incorrect code.
30858
Error when RE java files with comment in if/else statement -- in multiline statement
22906
Java/J2EE -> Apply Design Patterns on class does nothing
24511
RE of static attributes (class variables/attributes) from the type of the object itself
19219
File saved with absolute path when relative path should be resolved
16498
Java RE : Parser Error: near token }
13584
removing Roseuid during Java reverse engineering deletes activity diagram attached to operation
58229
The list of the files contained in a jar file does not get refreshed in the upper right window of the reverse engineer dialog
57424
Comment in synchronized statements won't RE
58417
Multiple classes (also class + interface) in the same file do not properly get reverse engineered
58582
Atatic roles are not generated as static attributes
57558
Import statements get dropped when opening and closing the component specification
58673
Missing methodbody via roundtrip-engineered java classes
57621
Renaming of a java class in Rose, makes rose to generate a new class to jbuilder
57737
Rose 2001a: Java Method bodies get lost while FE
57848
Auto synch checked: Can't get automatic updates for two classes assigned to the same component
60169
Loss of implementation with different logical and component view
60212
Return signature is incorrect after Java reverse engineering
61923
A member having the same type as of the class is deleted from the code during FE.
60528
Reverse Engineering the Java code uses class names as per the component hierarchy
55557
Unable to stereotype subsystem as <<EJBSessionBean>>
55617
I18N Korean comment gets corrupted after reverse engineering
56137
AutoSync doesn't work if JBuilder project under ClearCase control
56813
Unable to view try-catch code block in the Code tab of the operation specification
54211
Java Addin handles package name in Logical View inconsistently.
29426
Redundant parenthesis around operation statement causes Parser Error during java RE
29117
Compartment items do not stick during the reverse engineering process
29864
Java's "strictfp" causes parser error
18591
Java parser errors on comments that compile
16032
Generate Fully Qualified Type does not work for Container Class type causing incorrect code to be generated.
11400
Rose has trouble resolving fully qualified names in operation signatures
58228
RE java code rose hangs or crash
58931
Unable to reverse engineer java classes into Rose that have comments embedded in their method implementations
57743
Changing package name should change the folder name in Windows file system
57948
Can not open class specification on units write protected
60156
Common JDK classes as Fundamental Types may cause loss of implementation
07673
Java parser error on array instantiation
53679
Rose does not allow the EJB Remote Interface to extend more than one interface

Known Rose J Defects

Defect

Description

65055
Deploy WebLogic 6.1 EJB Classes missing in Jar file when the Temp DirectoryName includes a "." such as "myTempDir.01"
56595
In VisualAge persistence for a Container Managed EJB is recognized as Bean Managed.
54342
VAJ 3.2 is no longer supported
09370
In Operation specification Window under Code tab the read only field is not greyed out.
09262
Cannot Browse Source Code from C:\ (Root directory).


Rose Oracle8 Add-In

Rose Oracle8 Features and Enhancements

Rational Rose Oracle8 allows you to create object models from Oracle8 relational schemas and extend them to exploit Oracle8's object capabilities.

Rational Rose Oracle8 visualizes existing relational databases and facilitates the discovery and composition of existing business objects. This allows you to preserve your investment in existing relational databases while taking advantage of all the benefits that object modeling and development bring to desktop and server applications.

Known Rose Oracle8 Defects

Defect

Description

8201
Rose Oracle8 add-in supports only Oracle 8.0.5 or higher using Windows 98


Rose Model Integrator Add-In

Rose Model Integrator Features and Enhancements

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.

Rose Model Integrator Defects Fixed in this Release

Defect

Description

57124
Model integrator produces Multiple id:s after merging models
56372
Model integrator crash when comparing STL Utilities
57730
Merging models doesn't give proper result
58683
MI does not handle unnamed objects properly
18792
Model Intetgrator can't load cat files using UNC notation
60263
Model Integrator inconsistent merge result


Rational Quality Architect

Rational QualityArchitect is a powerful collection of integrated tools for testing middleware components built with technologies such as Enterprise JavaBeans and COM.

QualityArchitect, in conjunction with Rational Rose, generates test scripts for components and interactions in your Rose model. Once generated, the test scripts can be edited and run right from your development environment or from Rational TestManager.

With QualityArchitect, you can:

Rational QualityArchitect has its own release note. For more information on this product, select the Quality Architect readme file, which is accessible from the Start > Programs menu.


Rose Webgain TOPLink Wizard

The Rose Webgain TOPLink Wizard assists you in the final step of data modeling---data access. This wizard helps you create detailed data access mapping of your tables to your Java classes, for a persistent runtime environment, through integration into Webgain's TOPLink product.

Rose WebgainTOPLink Integration Wizard Defects Fixed in this Release

Defect

Description

28350
The Rational Rose Webgain TOPLink Wizard only supports TOPLink version 2.5. This addin now support 2.5 and 3.0.


Rose Type Library Importer Add-In

The Rose Type Library Importer Add-In allows you to import a type library of a COM component into the model by dragging the COM component from Windows Explorer and dropping it into Rational Rose.

You can control several aspects of how type libraries are imported into the model. For example, you can control:

Known Rose Type Library Defects

Defect

Description

16734
If you bring up the Import Type Library dialog by clicking Tools > COM , and you switch to another application and then return to Rose, Rose appears to hang. In this situation the active Import Type Library dialog is actually behind the Rose application window. Workaround: Minimize the other application(s) windows and press ALT+TAB until the Import Type Library dialog becomes visible again.


Rose Version Control Add-In

Rose Version Control Features and Enhancements

The Version Control Add-In, formerly known as the Source Code Control Add-In, provides integration between Rational Rose and any SCC-compliant version control system. It makes the most frequently used version control commands accessible directly from the Tools menu and from shortcut menus in Rose.

Upgrading from the Visual SourceSafe Add-In

The specific Visual SourceSafe (VSS) integration available in Rose 98i was incorporated into the Version Control Add-In in the Rose 2000 release. This Add-In now handles a super set of the VSS specific features. To upgrade a model that has been put under version control through the VSS Add-In, use the following steps:

1 . Make sure that the model is not open in Rational Rose.

2 . In Microsoft Visual SourceSafe, check out all the controlled units that belong to the model.

    Note: This cannot be done through the Version Control add-in because the add-in does not know the model is under version control.

3 . In Rational Rose, open the model.

4 . For each set of units that are located in the same SourceSafe project:

a . Click Tools > Version Control > Add to Version Control.

b . Select the units.

c . Click Browse and search for the project that corresponds to the working folder where the unit files are located.

d . Clear the Keep Checked Out checkbox, if you want to check in the units again.

e . Click OK.

Because the model is already under version control, the Version Control Add-In only updates the controlled units with additional version control information. From now on you can use the Version Control commands to check out and check in the units.


Rose Visual Basic Add-In

Rose Visual Basic Features and Enhancements

The Rose Visual Basic Add-In enables Rose to model, generate, and reverse engineer code for applications written in Microsoft Visual Basic. The Rose Visual Basic language support tools in Rose are tightly integrated with the Microsoft Visual Basic environment, allowing you to seamlessly progress through the round-trip engineering process.

The Rose Visual Basic Add-In tools are:

Rose Visual Basic includes a WinDNA code template enhancement. The fetch methods provided by the ADB.Fetcher code template for Visual Basic classes can connect to a database using either stored procedures or SQL statements.

Note: There is online Help for WinDNA code templates, but it is not completely integrated with the rest of the Rose online Help. For information on where to find the WinDNAHelp, search for WinDNA Code Templates in the Rose online Help index.

There are no new features in this release of Rose Visual Basic.

Rose Visual Basic Defects Fixed in this Release

Defect

Description

25775
Constants not shown in VB Model Assistant
55892
Rose VB Addin hangs with "Nested enum" in class
60846
Active X component can't create object using VB Addin

Known Rose Visual Basic Defects

Defect

Description

23767
Select project files in Visual Basics Component Properties Window not working
10932
On Windows 98, when you run VB scripts in the Model Update Tool in visible mode, a message will appear after you click Close on the summary page. The message Wscript says that the program has performed an illegal operation and that the program will be shut down. The message does not affect the functionality in the Model Update Tool or in Rose, and can be ignored by clicking OK. This message does not appear on the Windows NT, Windows 95, and Windows 2000 platforms.
16042
The WinDNA Code Templates are presented using DHMTL in the VB Model Assistant. Some problems have occurred when running these on Microsoft Internet Explorer (IE)version 4.0. The solution is to upgrade to IE version 5.x
23013
On the Visual Basic tab, accessible by clicking Tools > Options , the context-sensitive Help for the Visual Basic parameter properties ByVal, ByRef, Param, and Optional is missing. When you click F1 or Help, an error message appears. For Help on Visual Basic parameter properties, use the Help menu to open the Rose online Help and navigate to the Rose Visual Basic Help book. From the Visual Basic Help book, open the Reference Help book and click Model Properties.
Problem
The shortcut keys in the Visual Basic IDE are sometimes disabled when the Rose Tool window in Visual Basic is open. Workaround: Switch applications back and forth in the taskbar, or open and then close any dialog box in Visual Basic.
Problem
Rose Visual Basic does not work properly if Microsoft Visual StudioModeler is installed on the same computer. Workaround: Before installing Rose Visual Basic, uninstall Microsoft Visual Studio Modeler.


Rose Web Modeler Add-In

Rose Web Modeler Features and Enhancements

The Rational Rose Web Modeler provides visualization, modeling, and tools for developing Web applications.

To visualize and model N-tier web applications, Rose Web Modeler assigns a set of stereotypes and tagged values to your Web artifacts. Unified Modeling Language (UML) extensibility features allow you to model the artifacts required to build a Web application. Stereotypes and tagged values represent an extension of UML.

Setting Default Notation

We recommend setting the default notation to Web Modeler before attempting to model Web applications. This allows all directed modeling options to be present on the context menus. To set the default notation:

1 . Click Tools > Options.

2 . On the Notation tab, set Default Language to Web Modeler.

Rose Web Modeler Defects Fixed in this Release

Defect

Description

54305
When Web Modling is your default language, the specification window for states and activities can not be displayed
57551
Parser Error when reverse engineering code with strings containing quote characters
58794
Rose crash when deleting a web modeler attribute value

Known Rose Web Modeler Defects

Defect

Description

27391
Moving a virtual directory under another virtual directory is allowed by Rose, but can cause unpredictable round-trip engineering results. We do not recommend you do this. As specified in the help, a virtual directory may be nested under normal packages, but should not contain other nested virtual directories.
30462
Currently Web Modeler can resolve references between multiple virtual directories following the guidelines specified in the help. However, Web Modeler currently does not resolve references to fully qualified URLs, such as http://www.mycompany.com/mywebapp/mypage.html.
Turning off code generation
For every model element for which you can generate code, there is an option to turn off code generation. If you wish to model something, but do not want to generate code for it, disable code generation for the element. To access this option, open the element's Specification, and click the RTE Options tab.
Relationships to Java Beans and COM Classes
When an association is drawn from a JSP page to a Java class or from an ASP page to a COM class, you get custom dialog boxes with options that affect code generation. Currently, these options are not available for editing once the initial dialogs have been completed. Should you wish to make changes to these options, you must temporarily delete and re-add the association.


Rose Web Publisher Add-In

Rose Web Publisher Features and Enhancements

Rose Web Publisher allows you to publish Rational Rose models in HTML format. The Web Publisher Add-In exports your Rose model as HTML (including diagrams) so you can view them using a standard browser such as Microsoft Internet Explorer or Netscape Communicator. The Web Publisher also produces meta tags for use by search engines.

There are no new features in this release of Rose Web Publisher.

Rose Web Publisher Defects Fixed in This Release

Defect

Description

55024
Long descriptions do not fit to window when web publishing with Rose 2001a
56998
Settings in web publisher dialog are lost when the dialog is closed
56875
Component view links don't work correctly in HTML doc
56880
Web Publisher does not correctly handle targets in URLs added to packages/classes
55181
Published models do not show argument modifiers such as &.
19767
Web Publisher creates URL with /// when publishing document attached from a remote computer.

Known Rose Web Publisher Defects

Defect

Description

1488
Web Publisher keeps two Internet Explorer windows open.


Rose XML DTD Add-In

Rose XML DTD Features and Enhancements

The Rational Rose XML DTD Add-In provides visualization, modeling, and code generation to create XML document type definitions (DTD) for use in your application. You can reverse engineer an existing XML DTD to visualize a DTD's structure using a Rose class diagram. After modeling an XML DTD, you can use the Syntax Checker to validate your XML DTD. From the valid XML DTD model, you can generate code to create a new XML DTD.

In addition to reverse engineering an existing XML DTD, you can model a DTD using Rose class stereotypes for XML elements, element attributes, entities, and notations. By modeling an XML DTD, you can visualize the structure of the document to see which element definitions to change or remove. You can also share your XML DTD model with members of your development team to verify that you have captured the XML document requirements.

An XML DTD syntax checker finds errors in the XML DTD model, allowing you to make corrections before the DTD is implemented. Use the Generate Code feature to produce an XML DTD that you can test or implement in your environment.

To support mapping XML to UML, Rational Rose extends UML with stereotypes for XML elements, element attribute lists, entities, and notations. Stereotypes also represent XML operator symbols, sequence lists, choice lists, and element and element attribute multiplicity.

Note: DTDElementANY cannot be nested. Use this DTDElement at the root level.

Rose XML DTD Defects Fixed in This Release

Defect

Description

55061
XML-DTD reverse engineer fails when elements name is Japanese
29023
XML-DTD addin component documentation does not round tripKnown XML DTD Defects

Known Rose XML DTD Defects

Defect

Description

09129
Apply button not enabled for Component Spec window changes.


Rational Software Corporation  http://www.rational.com
support@rational.com
techpubs@rational.com
Copyright © 1993-2001, Rational Software Corporation. All rights reserved.