rose_readme.html" Content-Type: text/html Rational® Rose® Release Notes

Rational® Rose® Release Notes

Windows

© 2003 Rational Software Corporation. All Rights Reserved.

Any reproduction or distribution of this work is expressly prohibited without the prior written consent of Rational.

Legal Notices Information

Scope

These Rational Rose release notes provide:

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.

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 a software development 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 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.

Contents

Important Notice !! (Read before Installing)
What's New in This Release
Product Documentation
Hardware/Software Information
Client Requirements
Server Requirements
Getting Started
Core Rose and Rose Extensibility Interface
 Rose C++ Add-In’s  (ANSI C++, Rose C++, and Rose Visual C++ )
Rose Ada Add-In
Rose ClearCase  Add-In
Rose CORBA Add-In
Rose Data Modeler Add-In
Rose Framework Wizard
Rose J Add-In
Rose Oracle8 Add-In
Rose Model Integrator Add-In
Rose Quality Architect
Rose Webgain TOPLink Wizard
Rose Type Library Importer Add-In
Rose Version Control Add-In
Rose Visual Basic Add-In
Rose WebModeler Add-In
Rose Web Publisher Add-In
Rose XML DTD Add-In
Contacting Rational Technical Support

What’s New in This Release

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

IMPORTANT: Once the CORBA Model is converted by Rose 2003, it is no longer compatible with previous versions of Rose. It is important, upon upgrading to Rose 2003, no users perform work on this model in a previous version of Rose as this can cause model corruption.

Product Documentation

Additional product documentation is available in the following locations:

Hardware/Software Information

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.

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
  • If you are using commercial databases with Rose Data Modeler, we recommend installing those databases on dedicated machines.
  • Microsoft Access Runtime is automatically installed when you install at least one Rational Suite product on your machine. Sybase SQL Anywhere is available on the Rational Solutions for Windows CD, but it is configured to work only with Rational products.

IMPORTANT NOTICE!! Rational Installer Incompatible with Windows "Change Journal" Feature

Rational Installer Incompatible with Windows "Change Journal" Feature

Rational has determined that under certain circumstances file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has the Windows "Change Journal" (log) enabled on it. Therefore, the Rational Installer will not install to such partitions. Rational is actively working with Microsoft to better understand, repair, and/or work around the problem.

Before installing any Rational Version 2003 product onto a computer running Windows 2000, please read Rational Solution 182435434 at http://solutions.rational.com/solutions/display.jsp?solutionId=182435434 for the latest information. Alternatively, you can search the Rational Solutions Knowledge Base at http://solutions.rational.com/solutions for the text "Change Journal".

 

Additional System and Software Requirements

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

Rational Rose Requirements

Item

Minimum Requirements

Operating Systems
  • Windows NT 4.0 with Service Pack 6a and SRP (Security Rollup Package)
  • Windows 2000 with Service Pack 2 or 3 (English OS)
  • Windows XP with Service Pack 1

Hardware Requirements
  • Processor: 600 MHZ
  • RAM: 512 MB
  • Available Disk: Typical Installation – 720 MB, Compact Installation 173 MB.

Web Browsers

Rose add-ins that use a Web browser (for example, Web Publisher) support most common browsers.

Note: Because some Rational products (including some Rose Add-In's) may require certain Microsoft Internet Explorer components, if the Rational Setup program does not detect Internet Explorer 5.5 SP1 or SP2, or 6.0 SP1 on your system, you will be warned during the installation process - however, as this is only a warning, you may proceed with the remainder of the installation. Rose is tested with one of the recommended versions of Internet Explorer installed. Attempting to install and run Rose without Internet Explorer installed, may cause unpredictable results. You, however, are not required to use Internet Explorer as your browser.

Microsoft JVM

MS JVM Build 3809

Java

Rose J supports the following Java IDEs. Use the JDK appropriate to your IDE.

  • VisualCafe in Studio 4.0, 4.1 Standard, Professional, Enterprise, and Expert Editions
  • IBM VisualAge for Java 3.5, 3.5.3, 4.0 Professional and Enterprise Editions
  • Forte for Java Community Edition 3.0
  • Forte for Java Enterprise Edition 3.0
  • Sun One Studio 3 and 4 Community and Enterprise Edition
  • JBuilder 4.0, 5.0, 6.0, 7.0, 8.0 Enterprise, Professional and Foundation Editions

Network Server Requirements

If you use Sybase SQL Anywhere software, make sure that your database server meets the following minimum hardware and software requirements:

  • Operating system: Windows NT 4.0 Server or Workstation 4.0
  • Processor: Pentium
  • Memory: 64 MB
  • Disk space: 1.3 GB (minimum)
  • Network protocol: TCP/IP
  • Novell NetWare is no longer supported for network servers.

Rose Data Modeler Databases
  • DB2 Universal Database 5.x, 6.x & 7.x
  • DB2 OS390 5.x & 6.x
  • SQL Server 6.x & 7.x
  • Oracle 7.x, 8.x, and 9.x
  • Sybase System 12.5
  • SQL Server 2000
  • To reverse engineer Oracle and DB2 databases using Rose Data Modeler, an RDMS client must be installed.

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 or higher

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

The following files from LEAD Technologies, Inc., are included in this release:

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 has not been updated for this release. 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.

Note   Printed documentation not provided with Beta Release.

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.

Getting Started

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

General Guidelines

Note   You cannot run two different versions of Rose on the same machine. You must uninstall any previously installed version of Rose, before installing this release.  In addition, you will not be able to install this version of Rose on a machine, which contains any previous version of Rational products.

Licensing and Permissions Guidelines

Note   If you are required to reboot after installation, you must log on using the same administrator ID as the one you used to start the installation.

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:

The Replace files with newer versions in English check box is selected when you have installed earlier versions of shared files that are localized to a non-U.S. English language. If you clear this check box, you can save and print the list of files that need to be updated. You will need to update 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:

Rose path map variables are saved in the registry.

To backup path map variables:

  1. Run regedit and navigate to HKEY_CURRENT_USER\Software\Rational Software\Rose\Virtual Path Map .
  2. On the Registry menu, click Export Registry File...

To restore path map variables:

  1. Run regedit and navigate to HKEY_CURRENT_USER\Software\Rational Software\Rose\Virtual Path Map .
  2. On the Registry menu, click Import Registry File... and import the file you exported.

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.

Core Rose and Rose Extensibility Interface

Core Rose Features and Enhancements

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

Enhanced Pattern Content 

Users will have the ability to utilize Rose J Gang Of Four (GOF) patterns, as before. In addition, users may now access pattern content for additional languages - as described below. The user may apply a pattern through the context menu of a class or interface element defined in the tree browser or in the class diagram.

These GOF patterns are applied the same way you currently apply the Rose J GOF patterns, i.e.:

The participant Observer will show that it is bound to an existing model element (asterisk missing on its line).

All the other participants will be bound by default with classes named by adding the starting class qualified name to the (indexed) participant name. The asterisk at the right end of the participant row shows visually that it is not bound to an existing element in the model. If applied with these default names, the application will add these new elements in the model.

Select an existing element in the model for the remaining two SimpleParticipants (Subject and Client). If the type of the selected element does not match with the one declared in the XML file, the application will display a warning message.  You may select a new element with the right type or ignore the message. 

//Source file: C:\Test\ObserverApplied\ConcreteObserver1.java

package ObserverApplied;

public class ConcreteObserver1 implements Observer
{
private Subject subject;

/**
* @roseuid 3D7E719602A3
public ConcreteObserver1()
{

}

/**
* @roseuid 3D7E6FE90170
*/
public void update()
{
observerState = subject.getState();
}
}

Design Patterns Dialog Box Reference

The Design Patterns dialog box allows you to specify the participants for the selected design pattern. These are classes that will be added to your model, or classes that already exist in your model. The layout of the dialog box changes from design pattern to design pattern, displaying the participants of the selected design pattern only. The title of the dialog box matches the name of the design pattern you are applying.

Participants - The set of classes that make up this design pattern. Each class plays a role of a particular participant type. Each participant type labels a group of classes. Some groups contain only one class, others contain more. Initially, all groups contain names automatically generated by Rose. You can apply the design pattern using these names, and new classes with these names will be added to your model; or you can supply new ones. You can also substitute them with the names of classes that already exist in your model. If you do, Rose will not create new classes for you, but will use these classes instead.

Class Browser - Opens the Class Browser, from which you can select an existing class to use as a participant. This element appears when you double-click a participant class to edit its name. It is a gray button with three dots (an ellipsis).

Description - Displays design pattern information for the selected pattern. This includes an explanation of the kind of problem the design pattern solves, a brief overview of how it addresses the problem, descriptions of the participants that make up the design pattern, and a class diagram showing the pattern's structure.

Cancel - Discontinues the design pattern application process, and exits the Design Patterns dialog box.

The following elements appear in participant tables:

Add Participant Class - Adds a class to the selected participant table. It is a gray button with a small yellow starburst in the top left corner of a square.

Remove Participant Class - Removes the selected class from the participant table. It is a gray button with a red X.

 

Displaying ActiveX Controls

Rose may now be used as a container for all loaded ActiveX controls.

How To Perform the Rose / ActiveX Registry Configuration (Example: Microsoft Office Spreadsheet 9.0)

For example: HKEY_CURRENT_USER\Software\Rational Software\Rose\ActiveX

E.g.: To use the Microsoft Excel Spreadsheet (with ProgramID = "OWC.Spreadsheet.9" ) you should have the following key:

HKEY_CURRENT_USER\Software\Rational Software\Rose\ActiveX\OWC.Spreadsheet.9

How to Load ActiveX Control in Rose (once Registry steps are completed)

Upon restarting Rose you may now load any ActiveX control, which appears in the View menu option. Each ActiveX control (which, has been registered as described in "How To Perform the Rose / ActiveX Registry Configuration (Example: Microsoft Office Spreadsheet 9.0)" will list it's own menu option, directly under the Editor menu option.

Whenever an ActiveX control is created and loaded, it appears in the menu and the associated menu item is checked.

ActiveX Window Options in Rose

The size and position of the ActiveX window are saved into the registry when closing the Rose application.

To Close the ActiveX Control in Rose

Once the ActiveX control is loaded in Rose, it continues to be loaded until explicitly closing it.

ActiveX Feature Overview

The ActiveX controls project was added to the Rose workspace.  It is based on a SECMultiDocTemplate which creates a document and a view at runtime.  You can use Rose to load your COM object only if it is an ActiveX control.

A COM object is an ActiveX control if it exposes the following interfaces:

For each selected ActiveX, Rose creates the following:

IMPORTANT:

 

Ability to Easily Change Default Language

You may now change the default language, by right clicking on the bottom Rose window pane (which, currently displays the current default language).  A context menu will appear, with all language options.  Apply the new default language, by selecting one of the options presented in the context menu.

 

Core Rose and Extensibility Defects Fixed in This Release                         

Defect

Description

rose00085082

Problems experienced with copying and pasting in Sequence Diagrams.

RATLC00018205

Performance decline in Rose 2002, possibly related to presence of different model elements with the same name.

RATLC00024997

Error 3 reported by regsvr32.exe if attempting to VAJ Add-In and VAJ is not installed on the machine.

RATLC00030462

Including ":" Within the package name of a controlled unit can cause Rose to crash. It is important not to use the ":" character within a package name.

RATLC00040910

Dependency lines are no longer connected to the element's node after model reload.

RATLC00041364

Rose Printing, ‘Fit to Page’ condenses diagram (incorrectly) to fit in upper left corner.

RATLC00047429

Unresolved adornments in the Activity Diagram may occur when manipulating an object which is inside a swimlane.

RATLC00047430

Sequence Diagrams grow dynamically when scrolling and/or when refreshed.

RATLC00052915

Unable to unload a *.cat file if there is no name to the swimlane.

RATLC00053008

Rose: model with linked files performances decrease by 250%.

RATLC00053075

The *.exe used to install Rose is a zipped file may be unzipped manually, by right clicking on the *.exe and selecting to unzip.

RATLC 00053326

Activities resize when switching between diagrams.

RATLC 00054082

Model takes about 1.5 to 2 hours to load.

RATLC00054300

Sequence Diagram objects may move to the bottom of the diagram. This may occur when manipulating objects in the Class Diagram, and upon closing and opening Rose.

RATLC00054224

Printing layout does not retain.

RATLC00055021

Long lifelines appear on the Sequence Diagrams.

RATLC00055406

Deleting an object in Sequence Diagram may cause Rose to crash.

RATLC00211570

Role names on associations move when moving classes around or modifying the routing of an association. Workaround: The 'jump' behavior can be avoided by placing the role in the center of the line of association.

RATLC00212638

Running a specific script from Rose, would cause Rose to crash.  This was due to the diagrams being opened by the script not being closed (only hidden), thereby causing a loss of resources.

RATLC00212708

Print Preview can cause Rose to hang.

RATLC00213086

Containment property (role) documentation changes not updated in online Help.
The possible values for the collectionValid values should be listed as:
* Unspecified = 0
* ByValue = 1
* ByReference = 2

RATLC00213098

Circular Object Link relationship can cause Rose to crash.

RATLC00213105

Rose crash may occur upon trying to correct a corrupted association to class (from the association dialog box ("Detail Tab -> Link element" field)).

RATLC00213136

Saved Sequence Diagram not displayed correctly – actors repositioning lower upon redisplaying the diagram.

RATLC00213238

Messages on Sequence Diagrams can be lost, when moving and manipulating messages on the diagram.

RATLC00213295

Persistency is not shown in Rose, after reloading model.

RATLC00213310

Diagram reverts back to the 'original' diagram after having restructured it.

RATLC00213350

Rose may lose attribute or operation documentation after performing a copy and paste.

RATLC00213424

Invalid 'Unresolved Relation' warning messages may appear, as Rose is unable to resolve the transitions because they are in read-only controlled units.

RATLC00213447

Rose Online Help “SCRIPT_PATH” information updated.

RATLC00213473

Documentation of Collection.Count corrected in Online Help.

RATLC 213484, 227924

Problems displaying original object stereotype, after performing copy and paste in Sequence Diagram.

RATLC00213497

When viewing attribute types, long qualified names may cause dialog to grow too long causing scroll bars to disappear.

RATLC00213501

When opening Rose (indicating a read-only model name on the command line) or after loading a read-only model file and then attempting to activate a new Add-In (that has an associated *.pty file) from the Add-In Manger, or when attempting to open a model via the ClearCase Explorer errors will be displayed indicating the model is read-only.

RATLC00227839

Performing copy and paste of a sequence diagram may cause Rose to crash.

RATLC00227848

Slow model loading since moving from 2000e to 2002.

RATLC00227853

Sequence Diagrams dynamically grow too large to effectively access.

RATLC00229126

Printing and Web Publishing stereotypes for attributes and operations may be printed / displayed as black squares.

RATLC00231652

Absolute PATH is used for files in nested activities.

RATLC00231654

Rose may crash, after performing copy and paste in Use Case.

RATLC00365249

Creating an EJB, can cause Rose to crash.

RATLC00365897

Security setting problems could occur when attempting to install Rose on XP, unless installing as Administrator.

RATLC00366374

Unresolved (M) icons may occur when class diagram associations span controlled units.

Workarounds:

1.  Do a shallow delete (the DEL key) of the related class and then re-add the class to the diagram (i.e. by drag and drop) which will bring in the correct association; or

2.   Do a shallow delete (the DEL key) of the resolved association and then do a Query>Filter Relationships> OK.  This will re-add the correct association between the related classes.

RATLC00370128

Successive saves and reloads cause objects and messages in Sequence Diagram to reposition incorrectly upwards.

RATLC00370168

Downloading and installing release (Beta) could cause the following error when attempting to unpack and install:

Error:  1607 Unable to install InstallShield Scripting Runtime

Workaround:  Unzip the release manually and then run Setup to install.

RATLC00444103

Successive saves and reloads causes note anchors to incorrectly shift in Sequence Diagrams.

Known Core Rose and Extensibility Defects

IMPORTANT NOTICE!! Rational Installer Incompatible with Windows "Change Journal" Feature

Rational has determined that under certain circumstances file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has the Windows "Change Journal" (log) enabled on it. Therefore, the Rational Installer will not install to such partitions. Rational is actively working with Microsoft to better understand, repair, and/or work around the problem.

Before installing any Rational Version 2003 product onto a computer running Windows 2000, please read Rational Solution 182435434 at http://solutions.rational.com/solutions/display.jsp?solutionId=182435434 for the latest information. Alternatively, you can search the Rational Solutions Knowledge Base at http://solutions.rational.com/solutions for the text "Change Journal".

Defect

Description

rose00001575

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:

  • Start Rose from an MSDOS command line prompt by entering the following command: start rose.exe -noSplashScreen

rose00011555

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 box, click Properties .

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

4.   Click Extensions .

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

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

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

rose00011800

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.

rose00014249

A new Creates a Form class diagram toolbar is available, but you must manually add it to the toolbar.

rose00016544

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.
RATLC00213648 Rose may crash when switching to other applications while a model is being loaded.

RATLC00213154

Classes with “Automatic resize” option turned on, are created too wide.

RATLC000213677

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
RATLC00237076 Extended Help cannot be opened if RUP is not installed. This is correct behavior, however, this menu option should be grayed out in this circumstance.

RATLC00238101

Rose may consume a significant amount of CPU (i.e. 99%), if a Merant PVCS version prior to 7.5.00 is installed.  Work-around:  Disable the Version Control  Add-In, or do not install the Version Control Add-In when installing Rose.
RATLC00238431, 371412 Rose appends Virtual Path Map variable after drive letter if there are two equal folders on two drives
RATLC00238597 Multibyte character dialog will not appear. This will not change functionality, however, the warning dialog will not appear.
RATLC00238854 Help About - Characters may not display properly in Contact Information window on Korean Windows. The paragraph should read:

Before contacting Rational Software, please visit www.rational.com and www.rational.com/support for detailed product and contact information.

RATLC00239191

Rose may crash upon selecting New Model after undoing an Ojbject State deletion.

RATLC00239356

Unresolved transitions may be caused by copying and pasting Activity Diagrams containing decisions.

RATLC00239358

Unresolved ojbject flows may be caused by copying and pasting Activity Diagrams containing objects and object flows.

RATLC00239503

Do not apply Patterns under Use Case View.  When attempting to appliy GOF and Java Patterns under Use Case View Rose will hang.

RATLC00239845

“Java Virtual Machine error Main program not found” error may occur when attempting to access the Analysis Patterns in a Professional version of Rose.  Contact Technical Support, if this issue occurs.

RATLC00239886

Repair Installer functionality may not completely repair Rose installed files.  If you continue to encounter a problem, after running ‘Repair’, contact Technical Support.

RATLC00028780

Rose IDE Link mechanism does not correctly link to (or, integrate with) VAJ 3.5.3.  If encountering this problem, contact Rational Technical Support and ask for Technical Note# 16907.

RATLC00039665

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.

RATLC00039739

Print Preview does not work consistently for all diagram types.

RATLC00039964

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.

RATLC00040814

Text within the brackets on messages is lost on all sequence diagrams when user clicks Apply after changing the Message Signature option.

RATLC00040908

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.

RATLC00040964

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 .

RATLC00040969

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:

  • HKEY_CURRENT_USER\Software\Rational Software\Rose\Virtual Path Map
  • HKEY_LOCAL_MACHINE\Software\Rational Software\Rose\Virtual Path Map

RATLC00042172

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.

RATLC00042271

Deleting a package with a class attached to a read-only object in an activity diagram will cause Rose to crash

RATLC00042313

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.
RATLC00444954 A generalization and association may overlap each other, in diagram
RATLC00445804 Print Preview does not clearly represent activity diagram

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:

  • The Save Model and Model Update dialogs appear when the focus is on the running VB application (and not on Rose).
  • You must close Rose before the running VB application is stopped; otherwise a crash may occur.

Rose / ClearCase / RequisitePro Integration

This involves Rose models that use version control with ClearCase and integrated use cases with RequisitePro. If you have unsaved changes within a controlled package and attempt to check in that package, ClearCase prompts you to save your changes. In this case, RequisitePro does not recognize the save operation. When you subsequently close the Rose model, RequisitePro removes all changes since your last recognized save operation. Therefore, use case information in Rose and RequisitePro may not be synchronized. To avoid this, be sure to save the controlled package in Rose before checking it in to ClearCase.

 

Rose C++ Add-In's

Rose ANSI C++ Add-In

Rose ANSI C++ Enhancements Added in This Release

There are no new features or enhancements in this release of Rose

Rose ANSI C++ provides:

Rose ANSI C++ Defects Fixed in This Release

Defect

Description

RATLC00041185

No backups are made of changed files.   A new Module-Spec/Body property CreateBackupFiles, now controls the generation of backup files, but only when changes are detected.

The default is False. The file name is appended with a "~", and in the case of a 3 letter extension, the last character is replaced.

RATLC00041307

Dependency relationship not synchronized correctly.

Dependencies between ANSI C++ classes, stereotyped as #include, will cause generation of #include statement, as described in following scenarios:

Use Cases Supported

1. Create #include to header file

Create two classes (A and B). Draw a dependency from A to B. Set the stereotype to #include. Generate code. A.h will contain a #include of "B.h".

2. Create #include to an implementation file

The steps to be performed are the same as those above except that before code generation set the ANSI C++ property "BodyReferenceOnly" of the dependency to true. Now after code generation A.cpp will contain a #include of B.h.

3. Add a #include to a header file

Create two classes A and B. Generate code. Add a dependency from A to B. Set the stereotype of this dependency to #include. Generate code again. After code generation A.h will contain a #include of "B.h".

What is not supported:

Add a #include to an implementation file:

Defect RATLC00211772 states that #includes do not get added to implementation files when expected.

Remove #includes:

Removal of a #include dependency from the model will not remove the #include from the code.

Reverse engineer #includes:

#includes are from one source file to another. Because C++ classes can be split across many files and because multiple classes can occur in one source file it is not accurate to say that "class A includes class B".

RATLC00041805

Class Customization feature can generate two get or set operations for the same attribute, if the user invokes Class Customization twice, once generating Get by Reference and once generating Get.

RATLC00042531, 47423, 41795

Enhance the ability to generate Documentation (comments) during Code Generation, as well as Reverse Engineering and option to Synchronize (or not synchronize) Documentation (comments). See below, for further explanation and details**

RATLC0042653

Changing Inline property to true does not cause proper changes in code.

RATLC00047437

Reverse engineering /**/ comment containing blank lines may cause assertion error and crash.

RATLC00047392

Deletion of an attribute may cause bad updates when multiple declarators are in one declaration.

RATLC00049547

Incorrect source code generated when synchronize attribute declared on the same line.

RATLC00054406

Unable to get the ANSI C++ add-in in Rose to generate the classifier scope.

RATLC00211928

Create dummy containers for undefined classes on reverse engineer to avoid code loss.

RATLC00212576

Rose / ANSI C++ may hang upon reverse engineering a file that contains two enums, if at least one of the enums is a const enum.

RATLC00212912

Attributes declared on the same line, may go out of sync when round trip engineering.

RATLC00212994

Incorrect scope generated for nested ANSI C++ classes.

RATLC00213104

Changing the Output Directory (Tools>Options>C++-> Type: Project) after Code Generation will cause ANSI C++ Add-In inability to locate the source code.

RATLC00213170

Wrong initialization for static attribute in ANSI C++.

RATLC00213237

Performing code generation twice, may cause deleted class to again appear in code.

RATLC00213414

ANSI C++ reverses constructor with one abstract parameter declaration as reflexive aggregation.

RATLC00213538

Rose may crash upon converting Rose C++ to ANSI C++.

RATLC00229454

ANSI C++ converter crash on test model containing template instantiations.

RATC00233012

Allow choice of updating documentation during Reverse Engineering ANSI C++ code.

RATLC00365794

Static attribute is not updated in .cpp file after first time code generation.

RATLC00438920

Needs include without the relationship in ansi c++.

RATLC00438921

ANSI C++ Auto Synchronization mode generates wrong code.

**Documentation (comments) can be both generated and reverse engineered for all model elements.

Code Generation

Documentation is generated directly preceding the generated item and the items model Id. For example, the following code fragment shows generated documentation for two attributes within a class:

// The customer's date of birth.
//##ModelId=351ADC1EF002
CDate dob;
// The customer Id is used to record the
// unique Id given to each customer object
// in the system.
//##ModelId=351ADC1EF002
long custId;

The documentation text is converted into a comment block by generating single-line comments for each line of text. A space is automatically inserted between the single-line comment (//) and the start of the text. A line of documentation text may also begin explicitly with a comment delimiter, either a single-line (//) or multi-line (/*). The text is then generated as is in its entire form. This allows user-specific comments to be generated.

Reverse Engineering

Documentation can be reverse-engineered as well. Reverse engineering of documentation follows specific rules. From the code item's declaration, the code is traversed upward. A single optional blank line is allowed between the model Id comment tag and the end of the documentation comment block. If no model Id comment tag is found, a single optional blank line is allowed between the declaration and the end of the documentation comment block. The documentation comment block can use multiple single-line comments (//), multi-line (/*, */) comments, or a combination of both. However, only single-line comments (//) with a space will be converted to plain text. All other comments will appear as explicit comments in the documentation text. The comment block extends up until a blank line or another code declaration is reached.

Thus, to reverse engineer the documentation comment block, the code must be in the following format:

blank line or code
[ Comment Block
[ A single blank line ] ]
[ Model Id Tag ]
code declaration

The blank line will be preserved during synchronization; it can only be deleted in the source code.

Synchronization

The property CommentRules is used to control the synchronization of the UML documentation and the corresponding comment block in the source code. There are four choices available:

This supports full synchronization of comments in the model and source code. This is the default.

This setting will only generate comments into the source code, overwriting any comment section that differs with the documentation text.

This setting will only update the UML documentation for the associated entity, overwriting any text that differs from the comment.

This setting is used to turn off synchronization completely. This ensures that no updates will be performed on either the documentation or source code.

The property CommentRules can be set in the Properties dialog box under the ANSI C++ tab. Choose either the "Module Specification" or Module Body" type.

The property may also be set in the ANSI C++ specification of a component. Select the style tab and choose the appropriate setting under "Comments" in the "Round-Trip Engineering Options".

Prior Convention

Prior versions of the Rose ANSI C++ addin used a different style for generating comments in the source code. For example, the following code fragment shows generated documentation for two attributes within a class showing the old style:

//##ModelId=351ADC1EF002
//##Documentation
//## The customer's date of birth.
CDate dob;

//##ModelId=351ADC1EF002
//##Documentation
//## The customer Id is used to record the
//## unique Id given to each customer object
//## in the system.
long custId;

This style will be preserved, although no longer generated, as long as no model changes to the documentation text are made (if code generation synchronization is active). It is still possible to directly make any changes to the source code, and these can be synchronized with the model. However, should a change be required, stemming from a change in the model, then the old-style comment block will be rewritten to the new-style, and the comment block will be moved ahead of the model Id.

Known Rose ANSI C++ Defects

Defect

Description

RATLC00047641

Non inline operation bodies get generated in header file after round trip engineering.

RATLC00047676

Incorrect type qualification for exceptions generated with new Exceptions dialog.

RATLC00049391

Incorrect source code generated for attributes/parameters whose type is pointer/reference of enumeration/struct/union.

RATLC00049551

Incorrect source code generated in body file if operation's return type is a nested class.

RATLC00049794

Get by reference has return type of <type> & const.

RATLC00049796

No include and Forward Class Declaration, generated for association/generalization/dependency if the supplier class has CodeName.

RATLC00050181

Body file not synchronized during round trip engineering of template class.

RATLC00212596

ANSI C++ code generation -- need ability to generate all code to header file rather than to header and body file.

RATLC00212654

Forward Declaration/#include statement are not updated during subsequent code generation.

RATLC00368636

Rose ANSI C++ code generation does not generate class, enum and typedef in the correct order in the header file.

RATLC00600130

Friend class decl not removed from code during forward engineering.

 

Rose C++ Add-In

Rose C++ Features and Enhancements

Rose C++ Defects Fixed in This Release

Defect

Description

RATLC00042669

Setting “Forward Reference Only” on Parameterized class may cause Rose to crash.

RATLC0053166

Qualified name not used for nested C++ classes.

RATLC00054248

Forward engineering of a specific construct may cause the following Rose crash:

SYSTEM ERROR:  line xx, pc ..:  Cannot find property “GenerateInclude” in property set “default_Role”.

 Known Rose C++ Defects in This Release

Defect

Description

RATLC 238885

Rose Analyzer may write associated files to the Rose Release Area location, while in use.

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 .

 

Preliminary Feature – Limited Support for .NET 7.0

The Rose Visual C++ Add-In may now access projects loaded in the Microsoft Visual Studio .NET IDE.

Note    Rose Visual C++ Add-In does not support the .NET “managed C++” code extensions to the C++ language, at this time.  In addition, the Rose VC++ Add-In will not recognize the new “#” directives, added in .NET 7.0.

Enhancements have been made to the way modified files are handled.  By default, files that are open in the IDE and are modified by round-trip engineering will be modified directly in the IDE, thereby eliminating “file reload” messages.  This enhancement  also address a problem when using Rose Visual C++ in a ClearCase link directory.  File modification events are not delivered to the Visual C++ IDE when the files are in a ClearCase link directory.  Therefore the Visual C++ IDE would fail to reload the modified files into the IDE.  Now those files will be updated in the IDE with no “reload” message box dialogs.

How To Access .NET 7.0 Projects in Rose

The “Recent” and “Running” tabs will show VC++ .NET projects, as well as VC 6.0 projects.

Rose Visual C++ Add-In Defects Fixed in this Release

Defect

Description

RATLC00041560

VC++ role type and relationship not consistently linked together.

RATLC00055339

Comments on inline operations added twice to VC++ header file

RATLC00213032

Unable to work on a project when files have been moved from their original location.

RATLC00213384

VC++ Add-In appears to ignore namespaces when reverse engineering.

RATLC00214070

Operation comments added by the VC++ addin in the cpp file are not deleted when operation is deleted from Model.

RATLC00227834

#include not generated if the classes the dependency relates to are generated before the dependence was added.

RATLC00227928

Updated VC++ documentation in Online Help.

RATLC00231778

Updating the External Map does not affect the re-generation of the #includes in client classes.

RATLC00232264

Static Initializer declared in nested class lacks outer class scope in definition

RATLC00232265

Static Initializer in source is not recognized by the parser and is not updated

RATLC00438375

"int* const" gets changed to "int" when reverse engineering using VC++.

RATLC00439082

#include for aggregation and dependency ignores HeaderFileName property (was RBU21771).

Known Rose Visual C++ Add-In Defects

Defect

Description

RATLC00039535

Quick import in Model Assistant may not show all imported information until the window is closed and reopened.

RATLC00039545

Model Assistant should not show parameterized classes as override class.

RATLC00042021

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.

RATLC00042024

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.

RATLC00212957

mdl code causes Rose to un-assign interface from component in the model.

RATLC00231778

Updating the External Map does not affect the re-generation of the #includes in client classes.

RATLC00235393

Rose may delete implementation code for abstract destructors.
RATLC00237507 Error may occur when adding an attribute via Model Assistant. When this occurs, Rose process will continue running until the process is killed.
RATLC00238846 Entire "Options" groupbox should be enabled or disabled upon "Generate Documentation" check box change
RATLC00238955 Incorrect characters may be added after "[ ]" arrays if "::" is included within the "[ ]" array.

 

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

Rose Ada Problems and Limitations

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

Rose Ada Defects Fixed in This Release

Defect

Description

rose00014965

Rose/Apex needlessly reports circularities among nested packages.

rose00016142

Private only visibility for cg of operations.

rose00029061

Rose/Ada does not support RUP component view mapping.

The following settings are now supported for the Apex properties ApexSubystem and ApexView:

ApexSubsystem: [/]{directory/}subsystem ApexView: {directory/}view

rose00031390

Parameter mode field using Rose/Ada

A new parameter property Mode, is used to specify the parameter mode.  It is no longer necessary to specify the mode in the type field.

RATLC00234488

The following error message could occur, upon generation Ada95 code (which, includes many operations):

Error:  Internal Error:  The error type is unknown, an old type error id is used.

RATLC00039909

Context menu for a package should have "Browse" as an option.

RATLC00040027

Browse on a package does nothing if Apex Add-In is disabled.

RATLC00040199

CG property required to specify controlled type visibility.

A new class property TypeControlVisibility, specifies whether to make the controlled extension visible in the public part.  The default is Private.

RATLC00040756

Unable to code generate Ada83 / Ada95 from a read only model.

RATLC00040821

Allow completely private types.

RATLC00040865

Ada95 creates new file even when selecting no.

RATLC00041000

Error when trying to browse spec/body.

RATLC00041082

Browses to wrong spec after class is assigned to a component.

RATLC00041232

Unable to select multiple components for code generation in browser.

RATLC00041586

Type definition in package body.

RATLC00041617

Request for Representation property for association roles.

RATLC00042019

Apex and Rose/Ada: problems with code regeneration and checked in units.

RATLC00042861

Unable to change browse information in read only *.cat file after code generation.

RATLC00043143

Cannot browse body from component view - package body.

RATLC00047509

Update to Add-In Manager, to include Rose Ada Add-In minor version update number.

RATLC00047852

Add capability to generate Class wide Access Discriminants.

The new attribute/has/role property AccessDiscriminantClassWide controls whether type is generate as ‘Class.

RATLC00049240

Errors on code generation of overloaded operators (Unix only).

RATLC00053250

Rose Ada generates 'with' in the Package Spec when it could be in the Body.

RATLC00054636

Generation of generics in a package.

Supports subprogram generics only.  The stereotype of an instantiated class utility must be set to subprogram.  The class must also be assigned to a package spec component.  The Export Control field controls the location where the generic subprogram is declared.

RATLC00055342

Ada95 code generation of nested classes (level 3) raises a System Error.

RATLC00211903

Private constant not generated correctly.

ROSE00069859

Ability to specify a text file in the Copyright notice property.

A new property Declare, with the values (Before, After), can now be used to specify where the static declaration should be declared, either before or after the class type.

ROSE00073946

Suppress the generation of access procedures to public task entries of private task types (or any task type, for that matter).

ROSE00074511

Wrong signature generated in the Generic Subprogram Body.

ROSE00075639

Rose Ada: System Error: line 10811, pc 27607 Null Handle in request for property "inherits".

RATLC00212355

Ada 95 Browse Spec bring up the same code as Browse Body on Parameterized classes.

RATLC00212510

Subtype to be generated in private part.

RATLC00212616

Need Rose/Ada to maintain implementation declarations in body.

Export control or "class visibility" controls where the declaration is defined in the package spec/body.  TypeVisibility controls whether a public class is a private type.

A new class property

   IncompleteType (DoNotDeclare, NoDiscriminantPart, UnknownDiscriminantPart, KnownDiscriminantPart) is used to declare an incomplete type declaration.  The default is DoNotDeclare.

RATLC00212637

Unable to model a task that is completely private.

RATLC00212696

Generic subprogram instantiation for a class method.

Using the Export Control field on the instantiated class now controls the location where the instantiation is generated. The property CodeName is now supported.

RATLC00212878

Browse Body from a Class assigned to a "main Program" component doesnot work.

RATLC00214057

Ada can't generate missing directory during code gen.

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 Add-in Defects Fixed in this Release 

Defect

Description

RATLC00053584

After being presented with check box, listing components available to perform specific ClearCase action on and selecting only a few components, subsequent requests to perform the ClearCase action could result in error “There are no files available for the selected operation”.

RATLC00212948

Checkout Icon may not be updated correctly in Rose browser when using either full ClearCase or ClearCase Lt.

RATLC00213433

Registry setting “ShowAll=No” does not function correct.ly. 

RATLC00228252

Rose / ClearCase integration changed to utilize rmname rather than rmelem when user selects to Remove an Element from Source Control via the Rose menu options when performing ClearCase actions on Rose elements. The use of rmelem permanently removed the Rose object (requiring restoration of VOB backup, to recover file) while rmname includes ClearCase recovery options if user incorrectly chose this option. Note: The use of rmname requires the user be one of the following:

  • VOB owner
  • root (UNIX)
  • member of the ClearCase group (ClearCase on Windows)
  • Local administrator of the ClearCase LT server host (ClearCase LT on Windows)

RATLC00235769

ClearCase Checkin from Rose (via Rose / ClearCase integration) may not update icon in browser.

RATLC00235831

Using the Rose / ClearCase integration option to ‘Select All’ may cause ClearCase icons in the Rose browser not to be updated correctly.

Known Rose ClearCase Add-in Defects

Defect

Description

rose00016647

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:

This Release includes modifications to the CORBA Add-In actions involving attribute types, operation return types, operation parameter types, and operation exception types in Round Trip Engineering.

Existing CORBA Models will be converted (by this Release) to recognize and identify these changes, automatically during code generation when selected to be forward engineered, and during reverse engineering.  There is now one more phase during code generation - the CORBA conversion process.  You may notice performance degradation when performing code generation on an existing Corba model, the first time after installation of this Hot Fix, due to this additional conversion phase.

Note

If the type cannot be resolved in the model (i.e. the type cannot be found in the model OR if more than one type class of the same name is found in the model), the type would not be set and warning will be logged.  The following would be the warning message format:

[Resolving corba type references:  Start ]

WARNING:  Class <fully qualified class name> - operation <operation name> - <item type> cannot be resolved - '<type string>' will be used.

WARNING:  Class <fully qualified class name> - attribute <attribute name> - type cannot be resolved - '<type string>' will be used.

[Resolving corba type references:  Finish ]

* <item type> could be “parameter type”, “return type”, “exception type”.

If code generation is occurring on a read-only subunit OR read-only model, the conversion will NOT take place during code generation.  Hence, the type would not be set.  In this case you will need to make these units write-able for complete conversion.

IMPORTANT: Once the CORBA Model is converted by Rose 2003 (as described above), it is no longer compatible with previous versions of Rose. It is important, upon upgrading to Rose 2003, no users perform work on this model in a previous version of Rose as it can cause model corruption.

Rose CORBA Add-in Defects Fixed in this Release 

Defect

Description

RATLC00054223

CORBA Add-In does not recognize “#undef”.

RATLC00212301

CORBA Add-In does not use Logical View structure for storing type references.

RATLC00212792

Modifiers are placed inside parameter type definition – no quidu saved.

RATLC00368093

Order of operations/types not correct in resulting CORBA/IDL generated code.

 

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.

Defect

Description

RATLC00041558

Unable to suppress full PATH in #include in CORBA-code.

RATLC00234345

Unable to generate Value forward declarations.

 

Rose Data Modeler Add-In

Rose Data Modeler Features and Enhancements

Rational Rose Data Modeler is a database modeling and design tool that uses UML (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.

The Rose Data Modeler Add-In now supports Name Shortening in order to adhere to specific database requirements.  The new name shortening mechanism utilizes an algorithm to strip out vowels and to ensure uniqueness.  Name shortening is accomplished via Registry settings (prior to starting Rose). The following registry entries are set up automatically (using the default values for each supported database, as shown below) by the installer. To change these Registry settings:

  1. “Adaptive Server” with value 128
  2. “ANSI” with value 128
  3. “DB2” with value 128
  4. “Oracle” with value 30
  5.  “SQL Server” with value 128

Any names generated in the DDL that are longer than 128 characters (based, on the above settings) will be automatically shortened during the Forward Engineering process.  This feature, therefore ensures that all names generated in the DDL are valid in the database context of these strings.

Performance for Opening Table Specifications has been enhanced in the Rose Data Modeler Add-In.  Users will experience a significant performance enhancement when invoking the table specification, regardless of the number of relationships

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

RATLC00053912

Compare and Synch for Model is giving unexpected results.

RATLC00053751

Enhancement added to support shortened names.  Allows user to specify the length of name limitation (in registry file) in relation to the database being used.

RATLC00055157

Transforming an ANSI SQL 92 Data Model to an Object Model, Rose incorrectly transform a BIT(1) field to a String.

RATLC00055225

Timeout appears to occur when reverse engineering SQL database. A message may appear, indicating "The reverse engineering wizard was unable to complete successfully.  Please review Rose log for an explanation of the error. In the Rose log, the following is included in the messages '...[Timeout Expired]'. Workaround: It is possible this is due to network performance, due to a network interface. Deactivation from the network interface - the network connection to the SQL-Server will work faster, helping to complete reverse engineering successfully.

RATLC00055679

Errors encounter when attempting to parse Oracle 8 DDL.

RATLC00057930

Unique Constraints may be lost.

RATLC00212488

Character data type may be lost upon converting DDL into Object Model and back to original Data Model (DB2 7.x).

RATLC00213257

Alias in Views may cause java.lang.NullPointerException crash when performing Compare and Sync.

RATLC00213309

NUMERIC, NESTED, SEGMENT, LOB as names within DDL may causes parse errors.

RATLC00213339

Subquery clause of View fails if ORDER BY operator is utilized.

RATLC00213340

Errors may occur when attempting to reverse engineer package (Oracle 8).

RATLC00213342

Errors occur when using a trailing comma “,” in PROCEDURE clause.

RATLC00227840

Check constraints is not functioning correctly when applying only to columns.

RATLC00227912

Need to enumerate both user datasource and system ODBC datasource.

RATLC00228556

Performance Enhancement for deletion of tables.

RATLC00230034

Syntax Errors when reverse engineering Oracle 8 database.

RATLC00230248

Object Model to Data Model transformation may cause java.lang.NullPointerException Rose crash to occur.

RATLC00231658

Java.lang.NullPointerException occurs when reversing an Oracle SQL script which includes a DROP TABLESPACE statement.

RATLC00232848

NUMBER with size 0 in DB is wrongly reverse engineered to FLOAT with precision 0 in Rose.

RATLC00234217

Unnecessary “AS” generated during forward engineering with alias name views.

RATLC00234313

"NO USER DEFINED TABLE IN THE SELECTED DATABASE" error occurs when attempting to perform Compare and Sync.

RATLC00234807

Incorrect GUI for Compare & Sync of DB2 on OS 390.

RATLC00237446

Performance Enhancement when deleting Tables.

RATLC00365954

Compare and Sync generates NOT NULL for columns, although they should be NULLABLE (according to model).

RATLC00436852

Data Model to Object Model transformation information inconsistent in Online Help.

RATLC00439835

Unable to generate or open unique constraints.

RATLC00597453

Issues When Using TBCreator Field (only applies to DB2 OS 390 (MVS), Version 6x.
If the TBCreator field is left empty, the TBCreator field will automatically take the value of the UserID and Reverse engineer records created by the user ID.
When using the TBCreator field in the Reverse engineering Wizard, both the tables created by the UserID and the TBCreator specified are generated in the model. The tables created by the UserID will always be generated in the RE process regardless of whether a value is specified in the TBCreator field or not.

Known Rose Data Modeler Defects

Defect

Description

rose00054342

VAJ 3.2 is no longer supported

rose00056595

In VisualAge persistence for a Container Managed EJB is recognized as Bean Managed.
RATLC00237106 If the owner of tables in SQL 2000 is not dbo, the primary / foreign keys are not reverse engineered into Rose.

RATLC00237973

Unreferenced memory crash when performing reverse engineering on model from DB2 UDB to Rose.

This appears to be due to a database configuration issue when many long table names exist in the Database.  This can cause a query overflow on the server.  The workaround is to increase the heap sizes on the DB2 server to process more simultaneous requests.  To increase the heap size:

1.       Open the IBM DB2 Control Center

2.       Expand the Instances folder

3.       Right click the DB2 instance and click Configure

4.       Click the Performance tab

5.       Scroll to Query heap size,…,query_heap_sz

6.       Increment the existing heap size by increments of 1024 (Do not increase heap size to unreasonable value)
RATLC00371303 Rose may hang when adding an identifying relationship. When this occurs CPU will show as 100%.

RATLC00371353

Reverse engineering DB2 database and generate DDL produces incorrect column sequence.
RATLC00444561 Changing the parent constraint causes a new column to be generated.
RATLC00446595 Reverse engineering Count* in DDL causes a parser error.

 

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 round-trip engineering and provides support for large frameworks. This release of the Rose J add-in provides the following new capabilities:

J2EE Deployment

The Deployment Add-In which already provided J2EE deployment capability to deploy J2EE modules into application servers such as BEA WebLogic 5.1, BEA WebLogic 6.0, and IBM WebSphere 3.5 has been extended to provide EJB deployment for:

If you are building J2EE applications in Rose, now you can select the Deployment Add-In to deploy EJBs from Rose into the appropriate EJB container for Borland Application Server 4.5 or Borland Enterprise Server 5.1. A deployable JAR file is generated, which will allow you to deploy the JAR file into a particular partition of server.

The additional deployments to the Borland Application Server 4.5 and Borland Enterprise Server 5.1, are utilized in the same manner as the previous deployment options. The following describes these basic steps.

Steps Required Prior to Deploying Java Models

  1. Target Server (i.e. Borland Application Server 4.5 or Borland Enterprise Server 5.1) must be installed.
  2. Enable the Deployment Add-In from the Add-In Manager.
  3. Compile the Java files in Rose.
  4. Verify the compiled Java class directory matches the logical package structure for the Java classes in Rose.
How to Perform Deployment

                Editor for the XML deployment descriptors displays (if, selected)

 

Rose J / CM Integration

You may now place Rose J source code, XML files, EJB-JAR and WAR files into a Source Control System via the Rose J / CM Integration. You may also start the Source Control System Explorer from the Rose J Add-In.

Note   The Rose J / CM Integration only supports those Source Code Control Providers which support standard SCC API's.

Rose J / CM Integration Setup

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\ProviderRegKey

This key would be set to the value of one of the providers listed in the

HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\ProviderRegKey\InstalledSCCProviders

Setting (usually ClearCase or Microsoft Visual SourceSafe), according to the SCC provider to be used.

To select a location where the generated code files will be stored, click on the Select Source Root Path for Source Control button. Select the root path from class path for the source code. You may also edit class path from this dialog box via the Edit Class Path button. The root path is saved as a rose java property with Rose Model. The root path can be a virtual path, defined by Virtual Path Map from Rose.

If using ClearCase, the Root Path must be in a VOB

Example - Using ClearCase as SCC Provider with Rose J / CM Integration

The following describes a basic use case scenario of the Rose J / SCC Integration when using ClearCase.

Verify the ProviderRegKey registry setting is appropriately set for ClearCase as the SCC provider. If necessary to change the registry setting, restart Rose.

From the ClearCase Explorer, verify you have a VOB available where you wish to put the Rose J files under source control. Set the Source Root Path for Source Control to a directory in your VOB (see instructions in "Rose J / CM Integration Setup" within the Project Specification settings).

13:58:02| Component C:\Documents\joan\temp\joanac_view\JoanaVOB\myDemo\PkA\JavaA.java - Starting code generation

13:58:06| Add file C:\Documents\joan\temp\joanac_view\JoanaVOB\myDemo\PkA\JavaA.java to SCC successfully.

To Confirm Rose J Integrated Source Control Actions Performed

To verify that a new directory has been created and placed under source code control correctly under the selected project root path, for the package PkA and the *.java file (JavaA.java) - start the ClearCase Explorer, by selecting Tools > Java/J2EE > Use Source Code Control Explorer .

You may do the following in Rose and note the required CM actions are correctly implemented in ClearCase:

Right Click on the JavaA class in the diagram or in the browser and you will see the following context menu options, under the Java/J2EE selection:

 

Rose J Automatic IDE Detection

Once Rose is installed, you may use the Rose J Add-In to detect the existence of supported Java IDE’s installed on your machine.

Select the “Detect IDE button” (located in the J2EE / Java Project Specification on the Code Generation tab).  Once this is selected, the Rose J Add-In will automatically detect and allow you to integrate with supported versions of the following IDE’s:

Rose J will automatically detect all available / supported Java IDE’s.  You will have the opportunity to integrate with multiple IDE’s, using this new Rose J feature.

Enhancement to Include JDK 1.4 Framework

Rose J and J2EE Defects Fixed in This Release

Defect

Description

rose00072794

Java code can be deleted during code generation.

RATLC00018087

Parser errors can occur, when reverse engineering *.java file with nested “if” without braces.

RATLC00018283

Parent package’s *.sub and / or *.mdl file(s) need to be writeable to generate Rose J code.

Rose 2002 Release 2 included a new Rose J Code Generation requirement.  To successfully generate Rose J code - any associated *.sub file (if the *.cat files were controlled) and/or *.mdl file (if the *.cat files were not controlled) would have to be writeable.  If the necessary files were not writeable, an error message would be displayed and no Rose J code generation would not be performed.  This new requirement was added to Rose 2002 Release 2, in order to resolve:

RBU 72794 - Java code may be lost during code generation, after changing Component default or custom properties. 

In Rose 2003 the fix for RBU 72794 was re-engineered.

In Rose 2003, the user will be allowed to forward engineer a class when it’s component is inside a read-only sub control unit.  In this case, a warning will be recorded in the Rose log to alert the user  there may be an issue, for example – the following type of information would be recorded in the Rose log:

1.       When a user forward engineers a class for the first time or renames a class with autosync on or changes the virtual path from the path map and forward engineers the class, the following information would appear in the Rose log:

11:20:17| WARNING:  File D:\DMDefect\RATLC18283\test.sub is read-only – cannot save mapping information for file $TEMP2\P1\c1.java to component Component View::P1::c1.

2.       When a user forward engineers an EJB for the first time or the stereotype is modified, the following warning would appear in the Rose log:

11:40:12| WARNING:  File D:\DMDefect\RATLC 18283\test.sub is read-only – component stereotype is not updated for Component View::P1::aaEJB.

3.       When a user forward engineers a class after modifying the CmIdentification or CopyrightNotice property from the property editor, the following warning will appear in the Rose log:

11:42:04| WARNING:  File D:\DMDefect\RATLC 18283\test.sub is read-only – the CmIdentification information is not updated for Component View::P1::c1.

11:42:04| WARNING:  File D:\DMDefect\RATLC 18283\test.sub is read-only – the CopyrightNotice information is not updated for Component View::P1::c1.

RATLC00027867

Multiple dependencies created between the bean and classes when generating an EJB.

RATLC00041965

EJB classes created as Default Language (should be assigned to Java).

RATLC00047451

Unable to add suffix Remote to the Component Name while creating a new EJB.

RATLC00052722

Rose 2002 mixes @link and @param when generating javadoc for non-EJB operations.

RATLC00054964

Creating an operation with more than two parameters causes Rose to create an operation with parameters in wrong order for Remote Interface Class.

RATLC00055880

Parser error may occur when reverse engineering code with a typecast.

RATLC00056912

Code may be removed from interclass when forward engineering.

RATLC00212420

Not loading all the units may cause Rose to crash during code generation.

RATLC00212864

User defined tags do not get refreshed for existing classes when default @tags were enabled previously.

RATLC00213022

Updated Rose J Online Help to include explicit setup instructions for Java code generation.

RATLC00213156

Selecting an Entity Bean class and setting it’s persistent Property to true, causes the Bean Class to implement the Serializable interface.

RATLC00213199

Rose J operation body may be commented out when parameter exists in multiple packages.

RATLC00213222

Rose J unable to parse the reflection method properly while generating code.

RATLC00213747

Rose J parser does not recognize the class identifier used to access the outer class instance from a inner class method.

RATLC00213537

Javadoc comments for methods are improperly generated when performing code generation on an EJB.

RATLC00213635

Java RE & CG erroneously comments-out and moves some operations and code bodies to the end of the source file.

RATLC00213659

More than one Java throws clauses for operations cause an error resolving qualified name while reverse engineering.

RATLC00214007

Enhancement to include JDK 1.4 Framework.

RATLC00214056

CreateException and FinderException are not in model for EJB 2.0 CMP Local.

RATLC00214119

Rose – JBuilder 7 Integration – Blank entry in the ejbmodule tree when Reverse Engineering EJB.

RATLC00233010

Error may occur when Reverse Engineering java files with comment in “if / else” statement.

RATLC00365249

Creating an EJB may crash Rose.

RATLC00365313

Wrong file format reading EJB1.1 compliant ejb-jar.xml.

RATLC00365344

Unable to create CMP field.

RATLC00368252

For Interface classes, Rose J code generation deletes operations in the code, that are not in the model.

RATLC00368531

Generate Java code may produce invalid syntax errors.

RATLC00436230

Rose J parser error occurs when reverse engineering new InitialContext().

RATLC00440865

Code before Rose J reverse engineering not the same as code after forward engineering.

RATLC00441381

"Compilable" Java code gets removed or moved around during forward and reverse engineering.

 

Known Rose J and J2EE Defects

Defect

Description

rose00054342

VAJ 3.2 is no longer supported

rose00056595

In VisualAge persistence for a Container Managed EJB is recognized as Bean Managed.

RATLC00040971

Cannot Browse Source Code from C:\ (Root directory).

RATLC00040977

In Operation specification Window under Code tab the read only field is not grayed out.

RATLC00042697

Java Syntax Check on the J2SE1.3 Framework produces errors.
RATLC00211357 Carriage Return at the end of *.java file may produce a Parser Error.

RATLC00213636

Missing javadoc @param in the J2EE template (causes Warning in JBuilder).

RATLC00213654

JBuilder Integration:  Relationships between the second EJB components may be lost after reverse engineering more than one EJB modules.

RATLC00213731

JBuilder Integration:  Message-Driven Bean related classes may not get updated in Rose.

RATLC00213772

xxxLocal.java file in JBuilder is not updated when rename a ejb in Rose with autosync on.

RATLC00227846

EJB Deployment Descriptor "ejb-jar.xml" do not include "assembly-descriptor" information.

RATLC00229104

Rose J / CM Integration: Help buttons may not work correctly.
RATLC00238820 When using Rose / SunOne 4 integration - code may be generated to the original project assigned to the class, rather than a new project selected.
RATLC00239392 Autosync may stop functioning after deep-deleting a class. Workaround: Use Ctrl+G to manually perform code generation to restart Autosync.
RATLC00239503 Do not apply Patterns under Use Case View. When attempting to appliy GOF and Java Patterns under Use Case View Rose will hang.
RATLC00239705 When using the Forte IDE integration, the getservletInfo function is not updated.
RATLC00370940 Rose performance can be impacted when reverse engineering several classes with public final constants.
RATLC00371268 Parser error, when reverse engineering the following *.java code:

//--- http-Params
root.addContent(new Element("http-params")
//--- To
.addContent(new Element("To").setAttribute(new Attribute("value",this.from)))
//--- From
.addContent(new Element("From").setAttribute(new Attribute("value",this.to)))

RATLC00371334 Parser error may occur when reading *.java files stored on a UNIX/Linux share. Possibly misinterpretation of End-Of-Line terminator.
RATLC00444408 The following comments may cause a Rose J Parser Error:
Case 1:

public void no2() throws Exception, //comment causes parser error

ClassCastException {


}

Case 2:

public void no3() {

String s1 = "";

String s2

//comment causes parser error

= s1;

}

 

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.

Rose Oracle8 Defects Fixed in This Release 

Defect

Description

RATLC00434774

Updated Rose Online Help, regarding Foreign Key Wizard.

 

Known Rose Oracle8 Defects

Defect

Description

rose0008201

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.

Model Integrator – Ability to Log Conflicts to a File

Overview

The “Log Conflicts to file” feature enables the user of the Model Integrator to generate a hardcopy of the elements in conflict when comparing a number of up to 7 models.

How To Create “Conflict” Output File from Model Integrator

  1. The user selects and loads contributors in the Model Integrator application.
  2. The user selects “Compare”.

The model shows up in the Model Integrator with the first node with conflict selected and the property values for all the contributors displayed in the right section of the screen.  To log the conflicted items (of the entire model) to a file, select File->Log conflicts….  Note that this option is enabled ONLY if the application is in Compare mode.

  1. Once this option selected, you are prompted to enter the file name (in the Save As dialog box) where the items with conflicts (between contributors) should be logged, along with the values for each contributor.

Note:  The log file format may be text (*.log) or CSV (*.csv).  The CSV format enables you to open the file with Excel, which will provide a comprehensive layout.

Description of Model Integrator “Conflicts” Log File Output

The log file provides the user with the following information:

Rose Model Integrator Defects Fixed in this Release

Defect

Description

RATLC00054321

NULL disappears after merging mode with NULL.

RATLC213591

Merging *.cat files, using a base contributor may cause the Rose Model Integrator to crash with an access violation.

RATLC00228098

Relationships can be lost during merge activity.

RATLC00230575, RATLC00367538, RATLC00367566

RATLC 234656

Merging models with Rose Model Integrator can cause classes to appear more than once in the diagram.

RATLC00367538

Merging may cause duplication classes.

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

RATLC00042127

If you bring up the Import Type Library dialog box 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 box is actually behind the Rose application window.

Workaround: Minimize the other application(s) windows and press ALT+TAB until the Import Type Library dialog box 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.

  1. In Rational Rose, open the model.
  2. For each set of units that are located in the same SourceSafe project:
  1. Click Tools > Version Control > Add to Version Control .
  2. Select the units.
  3. Click Browse and search for the project that corresponds to the working folder where the unit files are located.
  4. Clear the Keep Checked Out checkbox, if you want to check in the units again.
  5. 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 Version Control Defects Fixed in this Release

Defect

Description

RATLC00213515

Rose may allow you to add subpackages to version control, even if they are read-only.

Known Version Control Add-In Defects

Defect

Description

RATLC00238101

Rose may consume a significant amount of CPU (i.e. 99%), if a Merant PVCS version prior to 7.5.00 is installed.  Work-around:  Disable the Version Control  Add-In, or do not install the Version Control Add-In when installing Rose.
RATLC00371809 When a file is attached to a package, Version Control operations (i.e. Check-in, Check-out, etc.) may cease to work.

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 Add-In Defects Fixed in this Release

Defect

Description

RATLC00018076

Rose Visual Basic code duplication after Updating Model from code.

RATLC00042565

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 .

RATLC00213207

Rose Visual Basic Help topics missing.

 

Known Rose Visual Basic Defects

Defect

Description

rose00010932

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.

rose00016042

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

RATLC00042647

Select project files in Visual Basics Component Properties Window not working

Problem Description

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 Description

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 Add-In Defects Fixed in this Release

Defect

Description

RATLC00211306

Use Case Specification doesn't open if default language is set to Web Modeler.

 

Known Rose Web Modeler Defects

Defect

Description

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.
RATLC00238871 Upon reverse engineering, notice a problem in the web page files - modifying / editing the web page file inside of Rose to fix the problem and then reverse engineering again will cause the modification in the web page files to be removed. Workaround: In this scenario, do not modify the file in Rose.

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

RATLC00214040, RATLC00365766

Hyperlinks to Activity icons in another package do not resolve in Web Published model.

RATLC00366254

Windows such as scroll bars and documentation may not appear in Internet Explorer, upon viewing a Web Published document.  This can be due to an incompatibility between SUN’s JDK runtime Java Virtual Machine and Microsoft’s Internet Explorer.

Workarounds (either option should work):

1.       Under IE | Tools | Internet Options | Advanced tab, uncheck “Use Java 2 v1.3.1_04 for <applet>(Requires restart)” option.  (Note: the JDK version might also be “v1.3.1_02”.)

2.       Uninstall the JDK version which appears to present the problem (1.3.1_04, 1.3.1_02, etc.) and install JDK versions, such as 1.3.1, 1.4.0, etc.

RATLC00442505

Web model file created by WebPublisher does not include the argument information of the Parameterized class.

RATLC00443524

WebPublisher does not create links for diagrams under a class.

Known Rose Web Publisher Defects

Defect

Description

RATLC00039560

Web Publisher keeps two Internet Explorer windows open.

RATLC00213284

Error occurs when Web Publishing a model which includes many sub-packages.

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.

Contacting Rational Technical Support

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

Your Location

Telephone

Facsimile

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 200 - Netherlands

+31 (0) 20 4545 202 -  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 be prepared to supply the following information: