IBM® Rational® Rose® Service Release 2003.06.13 Release Notes

Windows


Version 2003.06.13

Release Date: September 2004

Last Updated: 08/03/2004

Material ID/Part Number: GI11-5917-03


© Copyright IBM Corporation. 1992, 2004.  All Rights Reserved.

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

Legal Notices Information


These Release Notes are accurate at the time this product was prepared for release. The most recent version of this file is available in the IBM Publications at www.ibm.com/shop/publications/order. Search for GI11-5917-03 to find the latest version of these Release Notes in the IBM Publications Center. (To search for the IBM Publications Center, go to www.ibm.com and enter "IBM Publications Center" in the Search field.)


Scope

Product changes described in this document and contained within this service release apply to:

The Service Release Notes includes:

Getting Started

Installation Information

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

1.       Go to  http://www.ibm.com/software/rational/support/.

2.       Then, go to the Download Center and navigate to Rational patches and service releases.

Installation Issues

After Installing IBM Rational Product, Restart System Before Applying This Service Release

After you install a Rational product, you must restart your system before applying this service release. Do not apply this service release until you have restarted your system after installing a Rational product. See RATLC516372, below.

RATLC00516372 - If the Rational Setup Wizard does not appear when you apply this service release, use Windows Task Manager to end one of the msiexec.exe processes. The Rational Setup Wizard window should appear. If it still does not appear, cancel the next msiexec.exe. As a result, installation of this service release should be successful. Workaround: Restart you system before applying this Service Release.

Microsoft Windows 2000 NTFS "Change Journal" defect can cause file system corruption during installation of Rational products

Under certain circumstances, file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has enabled the Windows "Change Journal" (log). This corruption is caused by a defect in Windows 2000. Before you install any Rational Version 2003 product on Computer that is running Windows 2000:

  1. Disable all virus detection software
  2. Read IBM Support Technote 1135295. Go to http://www-1.ibm.com/support/us/search/index.html and search for "Rational Installer Change Journal."
  3. Read Microsoft Knowledge Base article 820888 at http://support.microsoft.com/default.aspx?scid=kb;[LN];820888.  This article includes information about an update from Microsoft that fixes the defect.

Microsoft .NET Framework (v.1.1 or higher) Required to Install Rose Data Modeler and Rose Web Modeler Add-In's

The Microsoft .NET Framework (v.1.1 or higher) is required to install the Rose Data Modeler and Rose Web Modeler Add-Ins.  If you do not have the required .NET Framework version installed and choose to continue the installation, these Add-ins will not be installed and previously installed versions of these add-ins will be disabled. You can install these Add-ins at any time after you install the .NET Framework by using the Change option of your Rose installation in the Add/Remove Programs in the Control Panel.

For additional information in relation to installing Microsoft .NET Framework, please refer to:

http://msdn.microsoft.com/netframework/technologyinfo/howtoget/default.aspx.

Installing Rose Enterprise Edition

The following describes Rose Enterprise Installation behavior in relation to the Rose Data Modeler and Rose Web Modeler Add-In's.

Microsoft .NET Framework Availability Installation Results User Action Required

New Installation

.NET Framework version 1.1 or higher is installed on the same machine on which installing Rose v2003.06.13. Rose Data Modeler & Rose Web Modeler install correctly. None
.NET Framework version 1.1 or higher is not installed on the same machine on which installing Rose v2003.06.13. General Install continues, however, the Rose Data Modeler & Rose Web Modeler Add-In's will not be installed. These Add-Ins may be installed at any time after you install the .NET Framework by accessing them from the Control Panel > Add or Remove Programs > Change button.  (Also see RATLC 247844, below)

Upgrade Current Installation

.NET Framework version 1.1 or higher is installed on the same machine on which installing Rose v2003.06.13. New v2003.06.13 Rose Data Modeler & Rose Web Modeler Add-In's install correctly and the previous versions of these Add-In's will no longer be available. None
.NET Framework version 1.1 or higher is not installed on the same machine on which installing Rose v2003.06.13. New v2003.06.13 Rose Data Modeler & Rose Web Modeler Add-In's do not get installed.  Previous version of these Add-In's are also deactivated. These Add-Ins may be installed at any time after you install the .NET Framework by accessing them from the Control Panel > Add or Remove Programs > Change button.  (Also see RATLC 247844, below)

RATLC00247844:  Installing Rational Suite Enterprise on machine which does not have .NET Framework version 1.1 or higher installed, warns that the Rose Data Modeler and Rose Web Modeler Add-In's will not be installed although the installation incorrectly attempts to proceed with installing these Add-In's.  These Add-In's will be listed in the Add-In Manager, however, you will be unable to active them.  These Add-In's should be re-installed (as described above in "User Action Required") after installing .NET Framework 1.1 or higher.

Installing Rose Data Modeler Edition

The following describes Rose Data Modeler Installation behavior in relation to the Rose Data Modeler and Rose Web Modeler Add-In's.

Microsoft .NET Framework Availability Installation Results User Action Required

New Installation

.NET Framework version 1.1 or higher is installed on the same machine on which installing Rose v2003.06.13. Rose Data Modeler & Rose Web Modeler install correctly. None
.NET Framework version 1.1 or higher is not installed on the same machine on which installing Rose v2003.06.13. Product Installation exits with error. Rose Data Modeler Edition v2003.06.13 may be installed at any time, after installing Microsoft .NET Framework version 1.1 or higher.

Upgrade Installation

.NET Framework version 1.1 or higher is installed on the same machine on which installing Rose v2003.06.13. New v2003.06.13 Rose Data Modeler version is installed correctly and the previous version will no longer be available. None
.NET Framework version 1.1 or higher is not installed on the same machine on which installing Rose v2003.06.13. Product installation exits with error. Rose Data Modeler Edition v2003.06.13 may be installed at any time, after installing Microsoft .NET Framework version 1.1 or higher.

Installation Notice Regarding Upgrade Installation of AnalystStudio

Some features included in AnalystStudio have duplicate component IDs causing issues with upgrades to this product. As a result, if you are upgrading IBM Rational Suite AnalystStudio v2003.06.01or v2003.06.12 to this service release, you must first uninstall AnalystStudio before installing v2003.06.13 of this product.

Attempting to install this release as an upgrade to IBM Rational Suite AnalystStudio v2003.06.01or v2003.06.12 will cause unpredictable runtime results as release files may not be updated correctly.


Known Issue:  
RATLC000245279
- The following AnalystStudio Rose Data Modeler Edition files will not update correctly when upgrading from v2003.06.01 with this Service Release:

  [Release_Location]\Rational\Rose\modelint.exe
  [Release_Location]\Rational\Rose\modelinit.dll
  [Release_Location]\Rational\Rose\Rose.exe
  [Release_Location]\Rational\Rose\roseres.dll
  [Release_Location]\Rational\Rose\datamodeler\RoseDataModeler.dll
  [Release_Location]\Rational\Rose\datamodeler\RoseDataModelerResources.Dll
  [Release_Location]\Rational\Rose\rosewebpub.dll
  [Release_Location]\Rational\Rose\rosewebpubres.dll
  [Release_Location]\Rational\Rose\rsssourcectl.dll

Workaround:
  Prior to installing this release, completely uninstall IBM Rational Suite AnalystStudio.

Rose RQA Add-In Requires Availability of the "File and Printer Sharing for Microsoft Networks" Service

The Rose RQA Add-In requires the "File and Printer Sharing for Microsoft Networks" service be available for use by the LAN Local Area Connection.  The Rose RQA Add-In is part of the Typical Installation.  Installing the Rose RQA Add-In without this service will result in the following errors:

"Error 1920. Service NuTCRACKERService (NuTCRACKERService) failed to start. Verify that you have sufficient privileges to start system services"

and / or

"Could not start the NuTCRACKERService service on Local Computer. Error 1075: The dependency service does not exist or has been marked for deletion."

To verify the service is available, select:

Start -> Settings -> Network and Dial-up Connections -> Local Area Connection (Properties) and verify "File and Printer Sharing for Microsoft Networks" is listed and checked in the "Components checked are used by this connection:" listbox.

If it is not listed, select Install -> Service -> Add... -> File and Printer Sharing for Microsoft Networks -> OK.

Product Documentation

Documentation for IBM Rational is available on-line at http://www.ibm.com/software/rational/support/documentation/.

Restrictions and Guidelines on Using Rose

Defects Fixed in this Release

Component

RATLC ID

Description

Rose Ada

RATLC00041562

Enhancement to support Ada95 Private types to be declared with unknown discriminants.
Rose Ada RATLC00043017 Multiple Inheritance Mixin Component Mapping problems.
Rose Ada RATLC00213208

Generation of an Ada package with a Use clause

The Additional Uses property specifies use clauses to be included in the context clause of the package.  For example, if the Additional Uses property is set to Ada.Text_Io for a subprogram module named Quadratic_Equation, the Ada Generator will output:

-- Additional Withs:

with Ada.Text_Io;

-- Additional Uses:

use Ada.Text_Io;

procedure Quadratic_Equation;

Only the library unit names should be listed in the Additional Uses property, with one library unit per line.

For Ada95, a use type clause can be specified by prefixing the subtype with "type".

Rose Ada

RATLC00237874

IsLimited=True does not work correctly when TypeImplementation=Mixin.

Rose ANSI C++ RATLC00047676 / IC40241 Incorrect type qualification for exceptions generated with new Exceptions dialog.
Rose ANSI C++ RATLC00049551 / IC38618 Incorrect source code generated in body file if operation’s return type is a nested class.

Rose ANSI C++

RATLC00059410

New attribute may not generate correctly if reverse engineering long single line intializer.

Rose ANSI C++

RATLC00245080 / IC38420

Assertion error may occur upon Reverse Engineering anonymous nested struct followed by multiple variable declarators.

Rose ANSI C++

RATLC00245182 / IC38572

#Include not generated correctly for dependency if BodyReferenceOnly=True and the body file has already been generated once.

Known Issues:
  • If the type of a method’s return is a nested class, the Fully Qualified name is emitted in the header file also.  This does not, however, cause any problem in compiling, meaning or usage of the code.
  • If after generating code once, the bodyFileReference is changed to False, the #include statement is generated in the header file as well without deleting it from the body file.
  • After generating code with bodyFileReference set to false, if the bodyFileReference property set to true then #include statement is not moved from the header to the body file.
Rose ANSI C++ RATLC00245452 / IC38770 Enhancement to enable the portability of Rose ANSI C++ Models from Rose Windows to Rose UNIX / Linux.

Rose ANSI C++

RATLC00372374

Enumerated types documentation is appended rather than correctly being overwritten.
Rose ANSI C++ RATLC00451571 Rose ANSI C++ does not support the "const" qualifier for operation return types, operation parameters.
Rose ANSI C++ RATLC00455350 / IC39979 Deleting class from Model does not correctly remove the class declaration in header file in Rose ANSI C++ (Japanese version of product).
Rose ANSI C++ RATLC00455372 / IC40011 Reverse Engineering and Forward Engineering a component does not work correctly in Rose ANSI C+ (Japanese version of product).

Rose ANSI C++

RATLC00455562 / IC40170

Reverse Engineering parameterized class may cause code loss.

Rose ANSI C++ RATLC0049551 Incorrect source code generated in body file if operation's return type is a nested class.
Rose C++ RATLC00243618 / IC37433 Incorrect code may be generated when an existing class is part of the return type.
Rose C++ RATLC00243968 Namespace is incorrectly generated in parameters.
Rose C++ RATLC00245350 C++ Namespaces are not being generated correctly.  For example, this occurs with a sample class, outer containing nested enum Inner.  This should be generated as:

Outer(Inner in = enum1)
Rose C++ RATLC00245437 / IC38741 If attributes have a specified initial value, copy constructor may initialize incorrectly.
Rose C++ RATLC00246091 Rose C++ Code Generator generates #pragma pack() instead of __packed__.
Rose C++ RATLC00457489 Incorrect C++ code generated with dependencies and nested classes.

Rose CORBA

RATLC00053118 CORBA Add-In removes all the new-lines from documentation of operation parameters.
Rose CORBA RATLC00213825 The Rose CORBA Add-In has been enhanced to allow repeated forward and reverse engineering of Corba IDLs.  It is important, however, that IDL files be reverse engineered in the decreasing order of dependency, i.e. the most dependent file be reverse engineered first and the least dependent file be reverse engineered last.

Rose CORBA

RATLC00239717

CORBA Specification controls are disabled when the model is read-only or checked in to source control.
Rose CORBA RATLC00241590 Rose CORA Add-In missing from Rose Professional C++ Release.
Core Rose RATLC00212520 Names of Events on State Diagrams position incorrectly when selecting statechart and moving.
Core Rose RATLC00213696 Rose may crash when running script  which tries to access "Name" property (using an external document) which does not exist for the object.
Core Rose RATLC00227925 Unable to disable "Automatic Resizing" for specific objects in certain diagrams.

An Automatic Resize option has been added in Sequence Diagram objects.  In this case, automatic resize of objects will now depend on the options settings.  In Collaboration and Activity diagrams, automatic resize is now consistent when editing the name in the dialog or directly in the diagram.  Automatic resize will depend on the option settings.

All diagram icons, except packages now have the same behavior according to the settings in Tools > Options > Diagram > Automatic Resizing.  This will control whether the icon is automatically resized to fit the icon's text.

Core Rose

RATLC00229074

Focus of control cannot be split and joined correctly.

Core Rose RATLC00238597 Multi-byte character dialog will not appear.  This will not change functionality, however, the warning dialog will not appear.

Core Rose

RATLC00243971 / IC37617

Copying and pasting Sequence Diagram containing messages associated to overloaded operations and then saving and reloading the model will cause both messages to appear on the diagram as referencing the first operation.
Core Rose RATLC00245329 Undo deletion of unresolved transition to self and nested activity may cause Rose to crash.
Core Rose RATLC00245330 Renaming a self-transition on an activity and then performing a copy / paste may cause Rose to crash.
Core Rose RATLC00245331 Pasting Activity with Transition to Self may crash Rose.
Core Rose RATLC00245332 Pasting after undoing delete from model may cause Rose to crash.
Core Rose RATLC00245333 Incorrect object flows are being created even when object flow cannot be pasted in the context.
Core Rose RATLC00245334 Decision should not allow self-transition.
Core Rose RATLC00245335 A Statemachine cannot be moved back to its original location.
Core Rose RATLC00245337 Stereotype icon does not display correctly, when the class reference is missing.  In this case, the object becomes very small and the actor icon doesn’t get displayed as the class referenced is missing.
Core Rose RATLC00245351 Deleting the upper Object Message may cause the lower return message focus of control to be missing.
Core Rose RATLC00245352 Creation Message to Object will generate incorrect sequence number.
Core Rose RATLC00245353 Creation Object not shifted down after copy and paste.
Core Rose RATLC00245354 Link Message numbers on Collaboration Diagram are not refreshed correctly after performing a copy and paste.  In this case, the Link Message numbers may have other characters overlapping on top of them.
Core Rose RATLC00245355 Rose may crash when deep-deleting Objects connected by Link Message with Data Token.
Core Rose RATLC00245356 The Ambiguous name dialog box should display when user cancels the changes via the "X" button.
Core Rose RATLC00245357 The Ambiguous Name Dialog should not display again after the user applies changes and clicks “OK” in the Specification dialog.  When the dialog displays again the second time, whatever the user chooses this time will overwrite what was chosen previously.
Core Rose RATLC00245358 Transitions cannot be dragged from browser back to Statechart diagram.
Workaround:  Use Menu Item Query / Filter relationship to add those views of the transitions back onto the diagram.
Core Rose RATLC00245359 Move Message to the top of the Object's focus of control results in double lined focus of control.
Core Rose RATLC00245360 Move Creation Message over an object message will loose focus of control and cause the numbering is wrong.
Core Rose RATLC00245362 Pasting nested state on Statechart diagram may cause errors to occur and Rose to crash.
Core Rose RATLC00245572 Rose may crash when deleting EJB operations.
Core Rose RATLC00245585 / IC37532 Rose 2003 fix for defect RBU 66331 has created side effect.
Classes with the “Automatic resize” option, become too wide.
Core Rose RATLC 00245586, 247001 / IC37981 Unable to update controlled checked-in unit, Font size too large.  Line feeds removed in class.  Classes and relationships do not display correctly (due to font size).  These issues occur in Rose (Japanese version).

Core Rose

RATLC00245588, RATLC00245600 / IC38816

Edited Model Properties do not persist upon closing and opening model.

Core Rose RATLC00245593 Cannot delete entries in the specifications files tab.
Core Rose RATLC00245607 Duplicate transition is created after renaming and pasting activities.
Core Rose RATLC00245608 Unnamed nested decision view may not be resolved after performing copy and paste.
Core Rose RATLC00245660 Unable to drag and drop nested transition from browser to diagram.
Core Rose RATLC00245663 The use of Rose Data Modeler stereotypes can cause the manual loading of the controlled unit to crash Rose.
Core Rose RATLC00245758 New operation on link message will create a new link message instead.
Core Rose RATLC00245764 The default font size is different in Rose v2003.06.00 compared to previous versions of Rose.  In previous versions the default font size was 10 and in Rose v2003.06.00 the font size is 12.  The larger font setting can cause distortions to previous models.

Workaround:  Change the font size under Tools > Options > General tab

Core Rose

RATLC00246320

Model property values do not persist when reloading model via REI.

Core Rose RATLC00246453 USER objects are not released properly on Windows XP after opening and closing context menu.
Core Rose RATLC00247001 Unable to update controlled checked-in unit, Font size too large.  Line feeds removed in class
Core Rose RATLC00248516 Importing a model created from an earlier version of Rose (prior to v2003.06.12) into Rose v2003.06.12 may crash after displaying some of the following Sequence Diagram warnings:

Warning:  Self message <name> relocated in diagram <name>
Warning:  Source updated for message <name> in Diagram <name>
Warning:  Destination updated for message <name> in Diagram <name>
Core Rose RATLC00248586 / IC41849 Model Properties (stored in a controlled unit *.prp) do not persist when the Model is loaded from a Workspace (*.wsp), or from the Recent tab of the Framework Wizard.
Core Rose RATLC00365509 Unable to draw a transition from H* to another state, although a state should include the ability to have a deep history substate H*.
Core Rose RATLC00365885 Changing the text of a Note, via the REI, doesn't correctly refresh after calling the diagram object's Update() method.

Core Rose

RATLC00367188

Page Setup (i.e. left and right margins & orientation) do not persist between Rose sessions.

Core Rose

RATLC00370484

Error may occur when inserting values on pathmap via script in Rose.

Core Rose RATLC00372346 Upon moving a Use Case from one package to another package, associations that belong to the Use Case view are not refreshed correctly in the browser.
Core Rose RATLC00372539 Opening Model changes element properties.

Core Rose

RATLC00372790

Browser view is not correctly updated upon closing the Specification window. 

Core Rose RATLC00375776 / IC41683 Rose displays an error dialog box in certain scenarios when running in automated mode.  This is resolved by redirecting the message toward the Rose log.

Core Rose

RATLC00438127

Attempting to remove an association from a class diagram by using RemoveItemView will not remove the subview for cardinality.  Upon selecting the 'dangling' cardinality may cause Rose to crash.

Core Rose RATLC00448955 Rose may crash if model and *.cat files are under ClearCase control and the file(s) are read-only when running a script on the model.

Workaround:  Rose will not crash, if the model is not in ClearCase control and/or the model and sub-units are checked out (writeable).

Core Rose RATLC00449542 Upon zooming out on a diagram or when printing the diagram to span pages (vertical and horizontal), text boxes will have text overflow of text outside the shape's boundaries.

Core Rose

RATLC00452964 / IC38788

Rose may crash when making a change in the Specification of a swimlane.
Core Rose RATLC00453921 / IC39110 & IC39419 Upon copying a package from a Use Case diagram, Rose may corrupt the diagram.  In this case, some of the objects may get 'circle-M's' although they are in the model.  The following is a reproducible example:

1. Load the unit into an empty model.
2. Open the use diagram Use_Case_Digram_Name in the package package_example.
3. Select the package package_example on the diagram.
4. Press CTRL + C to copy that package.
5. Shift focus to another running program (for example paste the Package into MS Word).
6. Go back to Rose.

Result: suddenly a few Use cases and the selected package appear to be missing from the diagram.

Core Rose RATLC00717022 / IC39550 Rose may crash upon loading model with duplicate association views.
Rose ClearCase RATLC00245440 / IC38702 Attempting to perform an "Undo Checkout" using Rose / ClearCase integration does not work correctly.  This occurs when the view's configuration spec includes a branching mechanism.  In this case, after performing an 'Undo Checkout' from the Rose / ClearCase integraiton - the object appears to no longer be under configuration management (ClearCase menu options grayed out) through the Rose / ClearCase integration.  ClearCase presents the object's configuration management information correctly.
Rose ClearCase RATLC00442547 Unable to add *.cat files to Visual Source Safe version control when packages are named the same.
Rose Data Modeler RATLC00018337 Reverse Engineering Wizard unable to complete successfully and no message is included in the Rose Log when the name of the database includes a space.
Rose Data Modeler RATLC00245342 Rose Data Modeler may generate the wrong column name when forward engineering.
Rose Data Modeler RATLC00245591 Deleting the Primary Key on the specification does not delete Foreign Key in dependent tables, and may cause Rose to crash.
Rose Data Modeler RATLC00245631 Addition of context menu option to allow user to enable or disable Rose Data Modeler Name Shortening feature for each Schema (see “To Disable Rose Data Modeler Name Shortening Enhancement” below).  In some cases, the view could become corrupt after forward engineering when using the Rose Data Modeler Name Shortening feature.

To Disable Rose Data Modeler Shortening Name Enhancement

A new menu option “Shorten Name Engine” is available on the Schema Data Modeler context menu, in the browser.  By default, you will notice that the “Shorten Name Engine” is enabled (the “√” appears directly before “Shorten Name Engine”) on the context menu.  The “Shorten Name Engine” option can be enabled or disabled per Schema.

All users working on the same model should use the same “Shorten Name Engine” option applied to the Schema, in order to avoid potential code generation differences.

Select Data Modeler > Shorten Name Engine (from the browser context menu for a specific Schema).   The √ will no longer appear in this context menu and the “Shorten Name Engine” will be disabled.

To again Enable the Shorten Name Engine, right click on the appropriate Schema and select Data Modeler > Shorten Name Engine.

Once “√” precedes “Shorten Name Engine” in this context menu, this feature is enabled.

Rose Data Modeler RATLC00245632 Upon upgrading to Rose v2003 view became corrupt when using Rose Data Modeler to forward engineer.
Rose Data Modeler RATLC00374432 Parent and Child Roles are seen in association specification, however, after reverse engineering a SQL DDL file, the associations are created but the Parent an Child role are left blank in the association.
Rose Data Modeler  RATLC00444486 Column length specification on diagram reverts to "0" (Rose will not accept the column length) when specifying the column type on a Data Model diagram as indicated below:

1. Put a table on a Data Model diagram, and add a column
2. Click on the column on the diagram (twice, slow) so that the cursor appears next to the column type
3. Erase the default column type and type 'VARCHAR(5)'
4. Click on the diagram space beside the table to enter changes

The column will show as 'VARCHAR(0)'.
Workaround:  Go into the Specification dialog for the column, to set it correctly.

Rose Data Modeler RATLC00450614 Unable to transform tables to classes when they have two identifying relationships.
Rose Data Modeler RATLC00453176 / PQ82034 When transforming an Object model, to a Data Model an empty schema is created.
Rose J RATLC00040767 Users may now create namespaces in Component View.  When a new class is created, user needs to create a component in Component view under the package which follows the Java package structure and assigns the component to the new class.  When Forward Engineering, the Java Class will be generated into the correct package with the correct namespace.  Refer to the following description.

1. Assume you want to generate a java class foo.bar
2. Assume that your company policy requires that all user packages be placed under the package USERCODE rather than under Logical View
3. Add package foo under package USERCODE
4. Add class c
5. Add package foo in Component View.
6. Add component c in package Component View::foo
7. Assign component c to class c.
8. Generate code for class c.

The package statement in the java file is package foo;

Rose J RATLC00052724 Line Termination is incorrect in Javadoc generated for EJB.
Rose J RATLC00053178 An error may occur when attempting to check-in reverse engineered model into ClearCase.  Error indicates field (java AllExceptions - properties in logical model) is greater than 8,000 characters.  AllExceptions duplicated in model each time reverse engineering.
Rose J RATLC00212086 Previously, to prevent including redundant import statements in Java file, Rose J would check the import list before writing import statement into Java file.  When a package was imported, those classes in the package would not be included in the import statements of a Java file.  In some cases, however, this redundant information is necessary to resolve ambiguity.  To resolve this issue, Rose J has been updated to write out those components with which the Forward Engineering component has dependency relations.  A component list is added.  All components which are listed in the imports list of the forward engineering component specification will be added to the list.  If a component appears on the list, it will be written into the import statement no matter whether it's package is imported.
Rose J RATLC00213245 Import statement is inadvertently removed when Reverse Engineering Java code into Rose.
Rose J RATLC00213488 Private class methods show as Public in xxLocalInterface when converting to EJB.  Rose J converting all existing methods in the class to business method (which is Public) without checking whether the original method is Public.
Rose J RATLC00232876 Warning occurs when attempting to generate code for a static class (static inner class), that has a static initialization block.  According to the Java Language Specification Document - an inner class cannot have a static initializer.  However, an inner class is a nested class which is not declared static (implicitly or explicitly).  If the nested class is either declared explicitly as static, or if it is an interface - it can contain a static initalizer.
Rose J RATLC00240540 Incorrect code will be generated when attempting to generate code for Rose J classes with the same names, but which are located in different packages.
Rose J RATLC00242008 Rose J Specification for components will override the default values to be blank.  Opening the Rose J Specification will blank out the default values.
Rose J RATLC00245340 Changing local interface to remote interface doesn't detect invalid *CMR.  No warning message is written into the Rose log.
Rose J RATLC00245341 Multiple Getter / Setter operations could be created when undeleting CMR association.
Rose J RATLC00245343 Unable to reverse engineer XML file that does not have rolename specified.  The rolenames in Rose should follow the CMR-field name in the XML file.
Rose J RATLC00245347 Multiple CMR's on bean are not imported when reverse engineering.
Rose J RATLC00245348 Getter / Setter methods are not created in Remote Interface.
Rose J RATLC00245349 Removing Navigable on a CMR does not remove Getter / Setter methods correctly.
Rose J RATLC00245431 Messages in relation to “Invalid CMR’s” are now written to the Rose log, rather than displaying a pop-up dialog.
Rose J RATLC00245572 Rose crashes when deleting EJB operations.
Rose J RATLC00245587 Japanese comments may become corrupt.
Rose J RATLC00245592 Setting return type (or attribute)  to "boolean" will automatically change to "Boolean".  The same problem occurs when setting "long", "byte", etc.
Rose J RATLC00245600 The EJB naming convention setting gets lost when reloading the model.
Rose J RATLC00374984 / IC37699 IC38570 Rose J failed to copy Java operations' documentation.  Rose J was getting the "OnNewModelElement" event and replacing the documentation for the copied item.  Now, the documentation is left 'as is' if it already exists.
Rose J RATLC00453853 / IC39064 Reverse Engineering error (Error Resolving Qualified Name) involving variable getting rewritten in a local scope.
Rose Model Integrator RATLC00246867
RATLC00453324 / IC38763
Add-Add conflict occurs, when performing a merge, if Model includes State diagrams which includes same named states.  Conditional added to determine whether the two 'state' nodes have the same set of ancestors and if so - will indicate a non-match.
Rose Model Integrator RATLC00456599 / IC40629 Add-Add conflict occurs if Model includes the same Class name in different Packages.  Parent support was added for Class diagrams so that the two same Class diagrams under different parents will not be matched.
Rose SCC RATLC00245361 LpAuxProjPath is not passed back to the Source Code Control Provider, which does not allow correct communication between Rose and source code control provider.
Rose SCC RATLC00039528 / IC38992
RATLC00444958
"Get Latest" option added to Rose Version Control Add-In which will allow users the ability to access all subunits of a loaded unit, even if the subunit (files) reside on another user's machine.  See Rational Rose Release Notes for more information in relation to this Rose Version Control Add-In Enhancement.
Rose VC RATLC00211743 Reverse engineering may be performed incorrectly when including an inheritance relation.
Rose VC RATLC00244694 Enhancement to utilize CodeFileName and HeaderFileName properties to populate the respective fields during Reverse Engineering.  Users may use this Enhancement by setting the Virtual Path Map "$MY_FILES_PATH".  If "$MY_FILES_PATH" is not set to include the Virtual Path Map, the "CodeFileName" and "HeaderFileName" will be populated with the absolute path and not the virtual path.
Rose VC RATLC00245339 / IC37751 Model assistant may crash after creating attribute "m_First" after then adding attribute with format of “:m_<string>First” for the same class.
Rose VC RATLC00247331 Rose may crash when Reverse Engineering VC++ files.

In addition, the following issues associated with RATLC00247331 are fixed:

  • If in a Function call there is a missing separator (as, shown in the example below) between the parameters, Rose may hang.  For example in the following context in the CRegistryAccess call there is a missing "," (comma) between the parameters 'key ="\\"' and 'COM_COMPONENT_NAME'

 

               CRegistryAccess(LPCSTR key="\\"COM_COMPONENT_NAME, HKEY
          registrySection=HKEY_LOCAL_MACHINE,LPCSTR keybase=REG_KEY_BASE);

  • Rose may be unable to correctly draw dependency for template class due to IDispatch Pointer becoming corrupt when Reverse Engineering in a large set of template classes, for example:

template <class T, BYTE c>

class __declspec(novtable) CS7Stack : public CS7StaQueBase<T, c>

{

}

A check was added to detect the corrupted COM data pointed to by IDispatch Pointer for template classes while setting up the dependency during Reverse Engineering of a large model.

  • Rose may crash or hang upon encountering a “*” between multilane comments, i.e. “/* text * text */”.
  • Passing a null pointer when encountering a template class in an internal function may cause Rose to crash.
  • Rose may hang upon encountering statements which are of type a = b that are put in a square brackets in a global context, as shown in the following example.

 [HKEY_LOCAL_MACHINE\SomeRegistryString=SomeRegistryValue]

Rose VC RATLC00369411 Rose VC Model Assistant does not offer possibility to change overridden operations properties (check boxes grayed out).  Check boxes will no longer be grayed out for virtual and inline methods when base class methods are overriden by the derived class.
Rose VC RATLC00439535 Enhancement to allow operations to be declared but not defined.
Rose Web Publisher RATLC00370436 Invalid E-Mail address in root.html page of Rose Web Publisher generated web page.
Rose Web Publisher RATLC00441783 Rose Web Publisher can cause an unnamed file error message when publishing to a network.  The same error can also occur when the model and external documents are on a local machine and the published documents path is on a network UNC address.

Workaround:  Publish the Model locally.

Files Add and/or Changed by this Release

Core Rose
[Release_Location]\rose\rose.exe
[Release_Location]\rose\roseres.dll

Rose Ada
[Release_Location]\rose\ada95\roseada95.pty
[Release_Location]\rose\ada95\roseada95.cx
[Release_Location]\rose\ada95\roseada83.pty
[Release_Location]\rose\ada95\roseada83.cx

Rose ANSI C++
[Release_Location]\rose\ansi c++\cppcvtk2.dll
[Release_Location]\rose\ansi c++\cppcvtk2res.dll
[Release_Location]\rose\ansi c++\cppdll.dll
[Release_Location]\rose\ansi c++\cppevent.dll
[Release_Location]\rose\ansi c++\cppres.dll
[Release_Location]\rose\ansi c++\resources.dll

Rose C++
[Release_Location]\rose\c++\rosecpp.cx

Rose CORBA
[Release_Location]\rose\corba\corba_addin.dll
[Release_Location]\rose\corba\corba_addinres.dll

Rose Data Modeler
[Release_Location]\rose\datamodeler\DMNET.dll
[Release_Location]\rose\datamodeler\Resource.dll

Rose J
[Release_Location]\rose\java\rjava_addin.dll
[Release_Location]\rose\java\rjava_addinres.dll
[Release_Location]\rose\java\ideLinkComponents\RJBuilderLink\RJBuilderReceiver.dll
[Release_Location]\rose\java\ideLinkComponents\RJBuilderLink\RJBuilderXLink.jar

Rose Model Integrator
[Release_Location]\rose\modelint.exe
[Release_Location]\rose\modelintres.dll

Rose VC++
[Release Location]\Rose\vc\dlls\resources.dll
[Release Location]\Rose\vc\dlls\rvc.dll
[Release Location]\Rose\vc\dlls\rvcapplicationstarter.dll
[Release Location]\Rose\vc\dlls\rvcatlassist.dll
[Release Location]\Rose\vc\dlls\rvcatltools.dll
[Release Location]\Rose\vc\dlls\rvccodeview.dll
[Release Location]\Rose\vc\dlls\rvccompprops.dll
[Release Location]\Rose\vc\dlls\rvccontrols.ocx
[Release Location]\Rose\vc\dlls\rvcdsputil.dll
[Release Location]\Rose\vc\dlls\rvcideaddin.dll
[Release Location]\Rose\vc\dlls\rvciface.dll
[Release Location]\Rose\vc\dlls\rvcimportmergemfc.dll
[Release Location]\Rose\vc\dlls\rvcimportmfc.dll
[Release Location]\Rose\vc\dlls\rvclangprops.dll
[Release Location]\Rose\vc\dlls\rvclangsupport.dll
[Release Location]\Rose\vc\dlls\rvcmdcnv.dll
[Release Location]\Rose\vc\dlls\rvcmdcnvres.dll
[Release Location]\Rose\vc\dlls\rvcmodelassist.dll
[Release Location]\Rose\vc\dlls\rvcprogress.exe
[Release Location]\Rose\vc\dlls\rvcres.dll
[Release Location]\Rose\vc\dlls\rvcrte.dll
[Release Location]\Rose\vc\dlls\rvcvs7addin.dll

Rose VS  
[Release Location]\Rose\vs\dlls\rvs.dll
[Release Location]\Rose\vs\dlls\rvsappstarter.dll
[Release Location]\Rose\vs\dlls\rvscac.ocx
[Release Location]\Rose\vs\dlls\rvscat.dll
[Release Location]\Rose\vs\dlls\rvscdlg.ocx
[Release Location]\Rose\vs\dlls\rvsclwiz.dll
[Release Location]\Rose\vs\dlls\rvscodeview.tlb
[Release Location]\Rose\vs\dlls\rvscomselect.dll
[Release Location]\Rose\vs\dlls\rvscut.dll
[Release Location]\Rose\vs\dlls\rvscwres.dll
[Release Location]\Rose\vs\dlls\rvsdlg.dll
[Release Location]\Rose\vs\dlls\rvsexplorercontrol.ocx
[Release Location]\Rose\vs\dlls\rvsim.exe
[Release Location]\Rose\vs\dlls\rvslangsupport.dll
[Release Location]\Rose\vs\dlls\rvsmut.dll
[Release Location]\Rose\vs\dlls\rvsprogressdialog.exe
[Release Location]\Rose\vs\dlls\rvsreporter.dll
[Release Location]\Rose\vs\dlls\rvsres.dll
[Release Location]\Rose\vs\dlls\rvsrichtextformat.dll
[Release Location]\Rose\vs\dlls\rvsrte.dll
[Release Location]\Rose\vs\dlls\rvsrtecontrols.ocx
[Release Location]\Rose\vs\dlls\rvssync.dll
[Release Location]\Rose\vs\dlls\rvstemplates.dll

Rose Version Control
[Release_Location]\rose\version control\dlls\rsssourcectl.dll

Rose Web Modeler
[Release_Location]\rose\web modeler\wm-xml.dll

Rose Web Publisher
[Release_Location]\rose\rosewp\rosewebpub.dll
[Release_Location]\rose\rosewp\rosewebpubres.dll

Release Notes
[Release_Location]\rose\doc\rose_readme.html
[Release_Location]\rose\doc\rose_readme_sr.html
[Release_Location]\rose\ja\doc\rose_readme.html
[Release_Location]\rose\ja\doc\rose_readme_sr.html

Note: 
[Release_Location] is the directory that the IBM Rational Products are installed in.  This is typically "C:\Program Files\Rational".

Contacting IBM Rational Software Support

The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Software Support homepage can be found at http://www.ibm.com/software/support.

Voice Support is available to all current contract holders via a telephone number in your country (where available). For specific country phone numbers, please refer to the IBM Software Support Handbook, Appendix B: Contact Information, found at http://www.ibm.com/software/support.