Rational Rose Service Release 2002.05.20.305.000 Release Notes
February 2002
Copyright
© 2002 Rational Software Corporation. All Rights Reserved.
This software contains proprietary and confidential information of Rational and its suppliers. Use, disclosure or reproduction is prohibited without the prior express written consent of Rational.
This Service Release fixes problems reported
with the v2002.05.20 release of Rational Rose.
What to Do If a “registry size” Error Occurs During Installation
Defects Fixed in this Service Release
Defects Fixed in Service Release v.2002.05.20
Defects Fixed in Service Release v.2002.05.01 (also,
included in this release)
Contacting
Rational Technical Support
This section lists the platforms on which this service
release can be installed. It also describes any changes to the hardware and
software requirements for Rational Rose Release 2002.05.20.
This service release is supported on the following platforms
Hardware requirements for this service release are the same
as those described in the installation notes for Rational Rose Release
2002.05.20
Software requirements for this service release are the same as those described in the installation notes for Rational Rose Release 2002.05.20
If you encounter the following system error, during installation of this service release:
Documentation for
Rational Rose is available on-line at http://www.rational.com/support/products/rose.jsp
This section describes any compatibility issues that could arise from use of this service release.
This service release does not introduce any compatibility issues with other Rational products.
This service release does not introduce any known compatibility issues with third-party products.
This Service Release provides no new or changed features.
rose00071347: 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.
rose00079812: Rose requires Internet Explorer version 5.01 SP 2 (rather, than Internet Explorer 4.01, as Rose Release Notes incorrectly indicate).
rose00080298: 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
rose00074071: No documentation in online Help about the Reference checkbox placed in the specification of a class.
The Reference checkbox is used to mark a class as reference in order to prevent modifying the source code of the class by generating code. When the Reference checkbox in the specification of a class is checked, Rose J cannot generate code (forward engineer) for this class.
The Reference checkbox can be checked in two ways.
1. Open the class specification and checked the checkbox.
2. Reverse engineer a class from a Reference Classpath. When the class is created in Rose, it is automatically marked as reference.
rose00086165: 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.
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.
This section describes defects that are corrected by this service release.
rose00014965 – Rose/Apex needlessly reports circularities among nested packages,
rose00016142 –
Private Only visibility for code generation of operations required.
rose00069859 –
Ability to specify a text file in the Copyright notice property required.
rose00071327 –
Ability to control the order of code generation in a package required. A new (attibute,has,role) property
Declare=(Before,After) can be used to control where the static declaration
should be declared - either before or after the class type.
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".
rose00022935 – Changing stereotype to <<parameterizedClass>> does not display until another code update occurs.
rose00058326 – Reverse Engineering of complex roles does not produce correct results.
rose00066172 – ANSI C++ code generated (‘Role A General’ Tab) incorrectly when autosync enabled.
rose00066567 – Associations disappear when performing C++ Model Conversion with autosync enabled.
rose00068936 – Macro defining namespace keyword causes entire namespace not to be reversed.
rose00071656 – Upon reverse engineering, class is not updated to parameterized class correctly.
rose00071890 – Converting to ANSI C++ from C++, attribute name is not generated correctly.
rose00074289 – ANSI C++ Converter crashes when converting a model with incorrect (inconsistent) C++ code.
rose00074305 – ANSI C++ Converter does not maintain association that was not code generated.
rose00074487 – Generation of ANSI C++ code for multiple modules
functions incorrectly.
rose00074615 – Upon converting from C++ to ANSI C++, association relationships no longer appear in the diagram but still exist in the class specification.
rose00074785 – Reverse engineering and generating code on the Orion component looses code.
rose00076415 – Converting to ANSI C++ from C++ may cause loss of association relationships in diagram.
rose00076485 – Converting to ANSI C++ from C++ fails if class is assigned to C++ Package Body and Spec components.
rose00077974– Generalization to instantiated class is not maintained upon ANSI C++ reverse engineering.
rose00079459 – Template instantiation is not reverse engineered correctly, after code is updated.
rose00079688 – Relationship not maintained, upon converting C++ to ANSI C++.
rose00081467 – Converting to ANSI C++ from C++ may cause crash if a class is not assigned to ANSI C++ component.
rose00081636 – No code generated when attempting to generate code on a generalization class after adding attributes.
rose00081653 & rose00022950– Source code not updated correctly upon changing parameterized class to a regular class in model and regenerating code.
rose00081785 – Creating a message between two objects on a Sequence Diagram, after performing other manipulations in the Sequence Diagram may cause Rose to crash.
rose00082000 – Rose crashes if add attribute (or operation) to a class with dependency to a C++ class and regenerating code.
rose00082093 – Function body not maintained in code, upon converting a class to a template and re-generating code.
rose00063576 – Selecting multiple items and right clicking in the diagram to display context menu, may cause Rose to hang. Workaround: After selecting multiple items in the diagram, use the Tools menu to select option or make selections and right click in the browser.
rose00078647 – Rose may hang upon opening ClearCase LT Explorer. Workaround: Close ClearCase LT Explorer in order to use Rose.
rose00065666 –
Incorrect package may be created under component view when RE a file that has
include statement to other file.
rose00070948 –
Incorrect IDL code generation for enums.
rose00056047 – File : "Save subunits of <...>" does not work correctly, when the Rose window is maximized. Workaround: This will always work correctly when the Rose window is minimized or upon selecting View : Toolbars.
rose00058660 – Fully qualified names for types in operation return and argument types are not updated correctly when the class is relocated.
rose00067865 –
Compartment items not maintained after copying and pasting operations, after
saving *.cat file.
rose00070964 – Transitions may no longer be properly linked to a Decision, after resizing the Decision.
rose00071257 – Rose may crash upon copying and pasting an activity
diagram which contains swimlanes and object flows.
rose00072192 – Focus of Control issues in Sequence Diagrams.
rose00072654 –
Messages may not get updated correctly upon moving operations between classes.
rose00074412 – Rose may crash upon performing an undo delete of class and interface in a controlled unit.
rose00075510 –
Unable to assign a custom size to a Focus of Control.
rose00076525 – Stereotype display icon (decoration) not always displaying correctly.
rose00076945 – Rose
may crash on second attempt to delete a write-protected association.
rose00077042 – File types such as ‘dtdFile dtd’ type (.dtd extension) may become associated with Rational Rose.
rose00079513 – Rose
2001a and 2002 models may not be compatible, due to the introduction of a new
‘quidu’ element designed to enhance performance. Upon using Rose 2002 to create an attribute of an array of
some other type in the model, Rose 2002 will store the internal reference
‘quidu’ to the base type. Upon
loading this model in Rose 2001a, the array type is lost as the type is based
on the quidu (which, Rose 2001a does not recognize. Rose 2002.05.20 introduces a new petal version format
(version: 46) to resolve this issue.
rose00080557– Crash may occur when state is moved and transition text label is automatically repositioned.
rose00081785 – Manipulating the contents of a Sequence Diagram (i.e. deleting elements, adding new objects) and then creating a message between two objects, may cause Rose to crash.
rose00082309 –
Connections can be lost between messages and operations in Sequence Diagram.
rose00021000 – Oracle columns having NUMBER type without width specifier are being reverse engineered as FLOAT type columns.
rose00025269 – Opening models created with previous versions of Rose could cause deletion of primary keys.
rose00026023 – Requirement to support Unicode and Unicode Big Endian file for Oracle parser.
rose00028329 – Help button on Oracle Tablespace Spec linking to SQL Server help topic.
rose00029869 – Unable to use Data Modeler:New when parent package is write protected.
rose00031323 – Data modeler requires write access to the model file.
rose00053698 & rose00082856 – Settings not retained correctly in reverse engineering wizard.
rose00054219 – Language default changes incorrectly to Data Modeler upon using Data Modeler to reverse engineer a DB from a database.
rose00054925 – Unable to update Table Specification in a write-enabled controlled unit nested in a write-protected controlled unit or model.
rose00056226 – Data Modeler duplicates the foreign keys when regenerating the data model.
rose00056320 – Visual defect when reassigning the schema to a new database.
rose00057794 – Unable to reverse engineer DDL script files using MS SL 2000.
rose00058227 – Transform to Data Model for Sybase does not function as expected.
rose00058674 – Reverse engineering a Sybase 12
Database may cause java.lang.ArrayIndexOutOfBound
Exception.
rose00066308 – Not Null values not retained in column specification.
rose00066487 – Unable to uncheck
Not Null Checkbox in Domain Specification Window.
rose00066530 – NOT NULL stays checked in domain types assigned to a column.
rose00070539 – Sorting columns may cause an com.ms.wfc.core.WFC Exception.
rose00070568 – Exception may occur when reverse engineering database - java.lang.IndexOutOfBoundsException: Insufficient space in SAFEARRAY.
rose00071609 – Upon to locate schema information upon attempting to reverse engineer in Sybase 12 database,
rose00071844 – Parser error (Error: Encountered “KEY”
at column n[xx]l) occurs when attempting to reverse engineer from DDL in Oracle
8.x.
rose00072171 & rose00082857 – Parser error on ALTER TABLE, PRIMARY KEY (Error: Encountered “KEY” at column n(T_n)) may occur upon reverse engineering in Oracle 8.
rose00072763 – Requirement to support Oracle 9i.
rose00073038 & rose00075794 – Error occurs upon attempting to reverse engineer DDL file which includes date type in Oracle 8.x.
rose00076731 & rose00082859 – DB2 parser error occurs upon attempting to reverse engineer DDL which includes REFERENCE clause.
rose00076802 – DB2 OS/390 reverse engineering issues if the table creator is not the same as the creator of the database.
rose00078479 – NULL value of Not Null not retained in specification dialog.
rose00080439 – Rose may crash upon transforming views from object to data model.
rose00081337– Not Null settings not retained correctly. Once domain is assigned UNIQUE checkbox is read only, which is correct. It is necessary to edit the domain for unique constraint, not from the column which has a domain data type.
rose00082856 – Reverse engineered DDL Script location doesn't persist after wizard is closed (...then reopened).
rose00086336
– Crash when reverse engineering
schema that does not belong to UserID and TBCreator is specified.
rose00058683
– Model Integrator does not handle
unnamed objects properly.
rose00066188
– Model Integrator performs merge
on unrelated diagrams, which results in a corrupt model. In this case, the diagrams being merged
were located in different state machines, different names and UID.
rose00075519 –
Include statement missing in *.h file after generating C++ code.
rose00024832
– New EJB CREATE method cannot be
created.
rose00030858
– Error when reverse engineering
java files with comment in if / else statement (in multiline statement).
rose00061221
– Error message (Enumerated value
public does not exist) may occur upon reverse engineering a servlet.
rose00066132
– Parser error may occur when
comment (i.e., //) is before
closing brace.
rose00067314
– Comments below Model ID are
removed after Round Trip Engineering.
rose00069341
– Convert to EJB assumes class
diagram is open and is currently the diagram in focus, when attempting to
display the newly created EJB.
rose00069564
– EJB*Local*Interface options not
available from Stereotype selection list.
rose00070075
– Code generation for package
names (i.e. those including spaces) may not be handled correctly (i.e. the
space may be deleted).
rose00070076
– Signature of operation are not
preserved when commented out at the end of the file.
rose00070206
– Java Component Specification
Imports tree sorting not sorting correctly.
rose00070359
– Reverse engineering can give a
reference to a class in the Java or Rose notation.
rose00070901
– Autosync does not update a class
when drawing a generalize from the interface it implements to another interface
with an operation.
rose00071212
– Java file is not moved into new
directory when moving the package that contains it to another package.
rose00071676
– EJB Local and LocalHome suffix
fields lose their default values.
rose00072794
– Code generation may cause loss
of data if both the *.sub and *.mdl files are read only. If only the *.cat and/or *.java files
are read only – the problem will not occur. This is resolved by checking whether the file for the model
file of the component is read only, prior to modifying the *.java file.
rose00073587
– Operation in nested class with
argument not fully qualified will reverse engineer incorrectly.
rose00075052
– Reverse engineering the rt.jar
file may produce the error – “Wrong file format… [path to *.class file[“.
rose00075210
– Incorrect code generated for
arrays in EJB business methods.
rose00075873
– Create EJB version 1.1 utilizes
EJB 2.0 dtd in the descriptor file.
rose00077011
– Support for the Java SDK 1.4 assert statement.
rose00077050
– Error (Error resolving qualified
name */IOException occurred in File C:\path\x.java) on comment between throws
and exception, if comment contains a comma.
rose00077112
– Error (Parser Error: near token
) on line n occurred in File C:\path\x.java) on comment inside an empty
operation parameter list.
rose00077113
– Error (Parser Error: near token
if on line n occurred in File C:\path\x.java) on comment between else and if
rose00077361
– Error
(Parser Error: near token { on line n occurred in File C:\path\x.java) on
comment for an anonymous inner class.
rose00077639
– Reverse
engineering error (Parser Error: near token char on line occurred in File
C:\path\x.java) on a comment in front of a method argument list.
rose00078100
– Code generation performed
incorrectly on array parameter (two brackets instead of one will be generated).
rose00078454
– Round trip engineering will
cause data loss if “)” is included in code.
rose00079333
– J2EE Framework model references
J2SE 1.2 components instead of correctly referencing the J2SE 1.3 components.
rose00079480
– Incorrect code generated upon
reverse engineering code when there are brackets in one line of code.
rose00079733
– Warning message added to log
when Rose J Add-in does not update getter and setter code.
rose00080317
– Significant performance
degradation when attempting to reverse engineer Java files.
rose00080697
– Location for ejb-jar_2_0.dtd
should be updated in EJB 2.0 deployment descriptor.
rose00081861
– Unable to reverse engineer
xerces.jar. Errors may occur, i.e.
Cannot assign a public class to more than one component). Rose may crash.
rose00074521 – Documentation does not get added correctly to the implementation file, upon attempting to generate code for a class that already has an existing *.cpp and *.h file – if these files already include documentation.
rose00076150 – VC++ code update performance
degradation.
rose00076667 – VC++ forward and reverse engineering performance degradation.
rose00079562 – Loosing “&” symbols in Rose VC++ arguments. (Also, see rose00079513 under Core Rose).
rose00077767 – Unable to open Web Modeler component specification.
rose00029061 -
Rose/Ada does not support RUP component view mapping.
rose00021101 – Conversion from C++ to ANSI C++ fails if class is assigned to C++ package body and spec components.
rose00031580 -
ANSI C++ should generate code for all fully qualified associations.
rose00056191 -
ANSI C++ reverse engineering of composition displays incorrectly as
aggregation.
rose00068559 -
ANSI C++ crash upon recreation of association after deleting it.
rose00065155 -
When a function with an exception specification returns a pointer to the array,
parser incorrectly handles as a data member. When such a function is static and has a definition, a crash
occurs.
rose00068321 -
Generating code on an association role name that has a specified type and then
immediately reverse engineering, the association is automatically converted to
an attribute instead of correctly remaining an association.
rose00069839 -
Assertion failure may occur upon selecting ‘Get’ and ‘Set’ check boxes when
performing class customization on an attribute that is an instantiated class.
rose00068178 -
Inheritance may be lost upon reverse engineering.
rose00012541 - Objects in a Sequence Diagram can overlap when performing
dragging operations.
rose00066331 -
Class icon ‘auto resize’ not functioning correctly.
rose00066855 -
Scrolling in diagram may cause crash on call to:
:__1cHCObjectIIsKindOf6kMpknNCRuntimeClass__i_.
rose00067057 -
Moving objects in Sequence Diagrams may cause unexpected behavior to
construction messages.
rose00068146 -
Allow Rose splash screen to go behind other applications.
rose00069961 -
When attaching a file to an instance of an object on an activity diagram, an
absolute path is saved rather than saving the file reference relative to the
closest PATHMAP variable.
rose00070855 -
Moving messages in Sequence Diagram can cause Rose to crash.
rose00054925 -
Unable to update Table Specification in a write-enabled controlled unit nested
in a write-protected controlled unit or model.
rose00056226 - Foreign Key is duplicated when transforming OM to DM.
rose00067981 -
Rose may crash when selecting 'NewDiagram' once an .mdl file merged by Model
Integrator is loaded in Rose.
rose00066681 - The
error [SYSTEM_ERROR line 1023, pc 7250 Reference to undefined
"isBodyPart"] halts code generation whenever a class in the model has
a dependency relationship to a non-instantiated parameterized class.
rose00027765 - Rose cannot automatically update fully qualified paths for argument types of classes relocated from one package to another.
rose00054211 -
Rose J handles white space and “&” characters in Logical View package names
inconsistently.
rose00057137 -
JBuilder class in package is not deleted in Rose even with autosync on
(JBuilder 6 is required for this fix to take effect).
rose00058432 -
Generating Java code for setters places custom source code in comments. Upon fixing this defect, the following
will apply:
The Rose J Add-In
will only add default code body for getter/setter if and only if the method
body in the code file is EMPTY.
In this way, any user-defined code will remain. This is also a
consistent behavior with the "generate default return line" feature.
If there is ever a case you change the attribute from one bean property type
(i.e. Simple) to another (i.e. Bound) and would like a new getter/setter method
to be generated in the code file, you may either:
rose00058944 -
Support for roundtrip engineering using the JBuilder "Folder"
specific feature.
rose00060169 - Rose
J loss of implementation when Logical and Component views differ.
rose00064897 -
When reverse engineering a parser error occurs when there is a comment between
the variable initializers.
rose00065574 -
Turning on GenerateFullyQualifiedTypes for attributes from model properties
causes Rose to stop using default.
rose00066704 -
Creating a final argument in a servlet operation (while autosync is active)
will generate the code in the argument name twice.
rose00068506 -
Rose unable to correctly locate the JDK that JBuilder installs.
rose00068949 -
Crash upon activating autosync and deleting component.
rose00069539 -
Error occurs (“an unnamed file was not found”) when relocating a module, while
utilizing the JBuilder IDE Link.
rose00070059 -
Reverse engineering Java class with association to itself, presents a class
with an association to an unspecified class.
rose00070215 -
Static initializers blocks may be deleted during code generation.
rose00070753 -
Rose may crash when changing the name of an entity EJB Primary Key class.
rose00070755 -
J2EE EJB - Converting to EJB can create duplicate attributes.
rose00071523 -
When round –trip engineering, if the class contains an operation with arguments
referencing other classes without being fully qualified – method bodies may be
deleted.
rose00071785 –
Java parser errors occur when trying to reverse engineer a java interface that
has “//” style comments on the line preceding the close brace.
rose00071877 -
Dragging a unidirectional association from a class to a servlet may leave rose
process running after exiting Rose.
rose00072290 -
Slow performance when reverse engineering.
rose00073819 -
When using JBuilder integration, Rose may erroneously indicate the project does
not contain any source files.
rose00074262 –
Round trip engineering Http Servlet may cause a loss of implementation code.
rose00030064 - Web Modeler stereotype icons do not display in
Sequence Diagrams.
No additional information is needed for this release.
If you have questions about installing, using, or maintaining this product, contact Rational Technical Support as follows:
|
Your Location |
Telephone |
E-mail |
|
North
America |
(800)
433-5444 (toll
free) (408)
863-4000 Cupertino,
CA |
support@rational.com
|
|
Europe,
Middle East, Africa |
+31
(0) 20-4546-200 Netherlands |
support@europe.rational.com
|
|
Asia
Pacific |
+61-2-9419-0111 Australia |
support@apac.rational.com
|
When you contact Rational Technical Support, please be prepared to supply the following information:
http://www.rational.com/support/index.jsp