Information copied from the following defect: RATLC Task ID: 230829 : OMSR2 - Rose Hot Fixes Description: Below, are the Hot Fixes available for Rose OM .20: Hot Fix 1: ---------- RATLC00053326: Activities resize when switching between diagrams. Hot Fix 2: ---------- RBU00085082: Problems with Copy & Paste - Sequence Diagram. Hot Fix 3: ---------- RATLC 227848: Slow model loading since moving from 2000e to 2002. RATLC 18205: Performance decline in Rose 2002, possibly related to presence of different name. RATLC 54082: Model takes about 1.5 to 2 hours to load. RATLC 213310: Diagram reverts back to the 'original' diagram after having restructured it. To Download and Install Hot Fix 3 or 5 (to, resolve the above issues): *To be installed in Rose 2002 Release 2 (2002.05.20)* 1. Verify everyone is logged out of Rose. Within command window: 2. Create a temporary directory and cd to this directory. 3. ftp ftp.rational.com 4. Login as the 'anonymous' account - using your complete E-mail address as the password. 5. Change to 'binary' mode 6. cd /public/V2002_r2/hotfix 7. get either 'Rose_7.6.0106.2203_omsr2_hotfix3.exe' or 'Rose_7.6.0106.2205_omsr2_hotfix5.exe'. (I understand the names of the Hot Fixes should be '7.7...'. Please, note - this naming was incorrect - however, the hot fix is appropriate and has been tested in Rose 2002 Relese 2.) 8. bye ftp Close command window 9. cd Rose directory and rename existing 'rose.exe' and 'roseres.dll' files (to save original copies). 10. Run the hot fix executable, to install in the Rose 2002 Release 2 release. 11. Start Rose. Hot Fix 4: ---------- RATLC00054964: Creating an operation with more than two parameters causes Rose to create an operation with parameters in wrong order for Remote Interface class. RATLC00365313: Wrong file format reading EJB1.1 compliant ejb-jar.xml. RBU00072794: Java code can be deleted during code generation. > Download and Installation Instructions for Hot Fix 4 > ======================================= > Requirement: Hot Fix 4 has been designed for and tested on Rose 2002 > Release 2 (2002.05.20). The user must have Rose 2002 Release 2 installed, > prior to installing Hot Fix 4. Once, Rose 2002 Release 2 has been > installed, perform the following: > > * Download > ftp://ftp.rational.com/public/V2002_r2/hotfix/RoseJava7.7hotfix4.exe > * Backup (rename) Rose\java\rjava_addin.dll and > Rose\Java\rjava_addinres.dll (prior, to installing Hot Fix) > * Double-click on RoseJava7.7hotfix4.exe (will extract and install > files into the C:\Rose_Location*\Rose\Java folder). > * Register rjava_addin.dll > * From the command prompt, enter: 'regsvr32 C:\Rose_Location > \Rose\Java\rjava_addin.dll' > Hot Fix, now installed. > *In many cases, Rose_Location is Program Files\Rational. If the > Rose_Location is not the default location, specified when double-clicking > on the Hot Fix, you will need to indicate the Rose_Location. The patched > files will, then, be placed in the Rose_Location\Rose\Java directory. > > Fixes for the following Defects included in Hot Fix 4: > ======================================= > > * RATLC 54964 - Creating an operation with more than two parameters > causes Rose to create an operation with parameters in wrong order for > Remote Interface class. > * RATLC 365313 - Wrong file format reading EJB 1.1 compliant > ejb-jar.xml > > Rose 2002 Release 2 Hot Fix 4 will also, help customers by providing a > Workaround for: > ================================================================= > > * RATLC 18283 - Parent package's *.sub and or *.mdl file(s) need(s) to > be writeable to generate Rose J code. > > A complete fix for RATLC 18283 will be available in McKinley. > > Workaround Description for RATLC 18283: > ================================= > Rose 2002 Release 2 included a new Rose J Code Generation > requirement. To successfully generate Rose J code - any associated *.sub > file(se) (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 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 . > > With Rose 2002 Release 2 Hot Fix 4, the user may elect to disable > the fix for RBU 72794. By default, the workaround for RATLC 18283 is not > enabled. By enabling the workaround, the user will encounter the original > Rose 2002 Release 1 behavior. The user will no longer be required to have > all associated *.sub and *.mdl files writeable, however, if the user > changes Component default or custom properties prior to generating Rose J > code and the associated *.sub and/or *.mdl files are not writeable, data > loss can occur. > > IMPORTANT: When using this workaround, to prevent potential loss > of data - one of the following MUST apply: > > * Do not change Component default or custom properties prior to Rose J > Code Generation; or > * Verify the *.sub and/or *.mdl files are writeable prior to Rose J > Code Generation > > To Enable the RATLC 18283 Workaround - Allowing Rose J Code > Generation without forcing the *.sub and/or *.mdl files to be writeable: > > -------------------------------------------------------------------------- > Once the Rose 2002 Release 2 Hot Fix 4 is installed, perform the > following steps to enable the workaround for RATLC 18283: > > * Prior to starting Rose, run regedit > * Within regedit, create the registry string value for > "GenerateOnReadOnly" (if, it doesn't exist) and set this value to "Yes". > (This is located under the key HKEY_LOCAL_MACHINE\\SOFTWARE\\Rational > Software\\Rose\\AddIns\\Java\\) > * Close regedit > * Start Rose (Workaround Applied) > ---- Hot Fix 5: ---------- RATLC 227848: Slow model loading since moving from 2000e to 2002. RATLC 18205: Performance decline in Rose 2002, possibly related to presence of different name. RATLC 54082: Model takes about 1.5 to 2 hours to load. RATLC 213310: Diagram reverts back to the 'original' diagram after having restructured it. RATLC 47430: Sequence diagrams grow dynamically when scrolling. RATLC 55021: Long lifelanes on the sequence diagram RATLC 227853: Sequence diagram goes off the page Please Note: In order to most effciently fix the Sequence Diagrams growing issue (Hot Fix 5), we had to remove a fix for RBU 72192 - FOCs problem in Sequence diagrams. In addition, one issue we are still encountering involves moving an actor in a Sequence Diagram, by dragging it to various positions. In some cases, this will cause poor positioning of the existing messages. We will need to address this in McKinley. This is a little better, but not yet fixed. If your customers notice any other issue which is presenting difficulties - please, let me know as soon as possible. To Download and Install Hot Fix 3 or 5 (to, resolve the above issues): *To be installed in Rose 2002 Release 2 (2002.05.20)* 1. Verify everyone is logged out of Rose. Within command window: 2. Create a temporary directory and cd to this directory. 3. ftp ftp.rational.com 4. Login as the 'anonymous' account - using your complete E-mail address as the password. 5. Change to 'binary' mode 6. cd /public/V2002_r2/hotfix 7. get either 'Rose_7.6.0106.2203_omsr2_hotfix3.exe' or 'Rose_7.6.0106.2205_omsr2_hotfix5.exe'. (I understand the names of the Hot Fixes should be '7.7...'. Please, note - this naming was incorrect - however, the hot fix is appropriate and has been tested in Rose 2002 Relese 2.) 8. bye ftp Close command window 9. cd Rose directory and rename existing 'rose.exe' and 'roseres.dll' files (to save original copies). 10. Run the hot fix executable, to install in the Rose 2002 Release 2 release. 11. Start Rose. Hot Fix 6: (see Attachment) ---------- 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. RATLC00213414 - ANSI C++ reverses constructor with one abstract parameter declaration as reflexive aggregation. RATLC00213538 - Rose may crash upon converting Rose C++ to ANSI C++. RATLC00041307 - Dependency relationship not synchronized correctly. 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. RATLC00042531, 47423, 41795 - Generating comments during code generation with "//", rather than "//##" and providing option to synchronize (or not synchronize) comments. 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. RATLC00213237 - Subsequently performing code generation again, deleted class will appear in code. 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. RATLC00227848 - Slow model loading since moving from 2000e to 2002. RATLC00018205 - Performance decline in Rose 2002, possibly related to presence of different name. RATLC 54082 - Model takes about 1.5 to 2 hours to load. RATLC 213310 - Diagram reverts back to the 'original' diagram after having restructured it RATLC00228252 - Rose / ClearCase integration changed to utilize rmname rather than rmelem when user selects to Remove an Element from Source Contol 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) RATLC00054321 - NULL disappears after merging mode with NULL. RATLC00213222 - Rose J unable to parse the reflection method properly while generating code. RATLC00214040, 365766 - Hyperlinks to Activity icons in another package due to resolve in Web Published model. Hot Fix 7 (created for ANZ): ---------------------------- It is designed to fix: Parser errors involving NOLOGGING and partitions associated with the DDLs you submitted, specific to Oracle; RATLC 53912 (We are looking into a potential problem with SQL queries). Paul currently thinks this has to do with the following (in relation to the customer's model) - we are still investigating: The remaining Compare and Sync issues are the result of the fact that the SQL script for the view is empty. While forward engineering, the 'CREATE VIEW' statement is generated according to the SQL script of the view. (See SQL tab on view specification dialog or 'SelectClause' attribute of the view in the *.mdl file.) If the SQL script is empty, the 'CREATE VIEW' statement will not be generated for this view. The SQL contents for all 116 views are empty, so no 'CREATE VIEW' statement for these 116 views in DDL file. This is why the difference is reported. FE of Float and Number (This is resolved for the newly created column. If you create a new data type, such as float or number - default length will be applied. And, I am checking with Paul on the following statement: The user will need to manually change all the float data types which have a length of '0' in the existing model to work around the problem.) Comments with single quotes (This issue is fixed for single quotes - for the beginning and ending single quote marks. However, Rose does not recognize 1 - n quote marks in the comments field after forward engineering. In this case, Rose will only keep one quote mark and there will be differences in the Compare and Sync for comments. We would want to let the customer know, that currently multiple quote marks are not supported. We could enhance Rose to accommodate this in a future release.) Please, let me know if you feel this will be a problem for the customer (i.e. they are utilizing more than one quote mark). Hot Fix 8: ---------- This is intended to resolve: Performance for Opening Table Specifications. We should expect a relative short and constant time (say < 2 second) to invoke table specification regardless of the number of relationships. Before the changes, it could take 5-10 minutes on tables with 50+ relationships. Installation: Back up files ' rename \Rose\DataModeler\RoseDataModeler.Dll to OLD_RoseDataModeler.Dll ' rename \Rose\DataModeler\RoseDataModelerResources.Dll to OLD_RoseDataModelerResources.Dll ' rename C:\WinNT\java\trustlib\RoseDataModeler.zip to OLD_RoseDataModeler.zip ' is the directory that Rational Rose is installed in. Typically this is C:\Program Files\Rational\ ' Replace the above files with files from OMSR2_hotfix8_DMperfimprovement_11.15.2002.zip Hot Fix 9: ---------- Fix for significant Model Integrator Merge Issues: RATLC 230575 - Merging models with MI makes classes to show up more than once on diagrams RATLC 367538 - Merging is causing duplicate classes RATLC 54231 - SR3HF: null disappears after merging model with NULL Installation: Back up files rename Modelint.exe to OLD_Modelint.exe rename Modelintres.dll to OLD_Modelintres.dll Double Click OMSR2_hotfix9_11.20.2002_MI.exe and unzip to \Rational where Install_Dir is the directory that Rational Rose is installed in. Files will be placed into \Rational\Rose Hot Fix 10: ----------- Fixes Checkout, Checkin, and Undo Checkout browser icon updates when Rose integrates with ClearCase: RATLC 212948 - Checkout Icon not updated in Rose with full CC and CCLT and Rose from Suite 2002 RATLC 235769 - NYT: clearcase checkin does not update the icon. Notes: Need to unregister and reregister the hot fix .dll's from the same location before it starts working for the above defects to pass. RATLC 235831 - NYT: clearcase select all and checkout icon does not work properly The select all still doesn't work. You have to exit rose and restart and load the model to see the checkout icons. Reloading with out exiting rose doesn't work Installation: Back up files rename clearcase_addin.dll to OLD_clearcase_addin.dll rename clearcase_addinres.dll to OLD_clearcase_addinres.dll Double Click OM.20_hotfix10_Clearcase_NYT_01.21.2003.exe and unzip to \Rational where Install_Dir is the directory that Rational Rose is installed in. Typically this is C:\Program Files\Rational\. Hot Fix 11 (IRS PRIME): ----------------------- This Hot Fix includes the following enhancement and defect fixes: Enhancement to produce log (*.csv file) output when performing Model Comparisons. Follow the attached description of steps which may be used to create and view the new Model Integrator log file. (See attached 'Steps for logging conflicts.doc') Defects Fixed, in this Model Integrator Hot Fix: RATLC 228098 - Relationships can be lost during model merge. RATLC 230575 & RATLC 367538- Merging models with Model Integrator can make classes appear more than once in diagrams. RATLC 54231 - null disappears after merging model with NULL. Please Note: We discovered a defect in the Model Integrator (not an issue customer reported or requested a fix for and a problem which is not a regression - appears to have been an issue in the Model Integrator in previous releases as well). We are working toward resolving this issue in McKinley Rose: RATLC 234656 - Merging two models, in which the only differences were their relationship properties - duplicated classes To Download and Install the Model Integrator Hot Fix: Location: \\rbubld00red\build\omsr2\hotfixes\om.20_hotfix11_MI_IRSPrime_12.23.2002.exe To Install Model Integrator Hot Fix: Install Rose Enterprise from OM .20 (Rose 2002.05.20) Back up Files: rename Modelint.exe rename Modelintres.dll Double Click om.20_hotfix11_MI_IRSPrime_12.23.2002.exe and unzip to \Rational where Install_Dir is the directory that Rational Rose is installed in. Files will be placed into \Rational\Rose. Hot Fix 12: ----------- This Hot Fix provides JBuilder8 IDE Link support in Rose OMSR2. Your users may access this Hot Fix from: ftp.rational.com://public/V2002_r2/hotfix/OM.20_hotfix12_JBuilder8_02.03.2003 Please, refer to the instructions below designed to describe how to install this Hot Fix. Note: This Hot Fix includes automatic IDE Link detection from Rose J, once the supported IDE Link is installed! Installation: Install Suite Enterprise from OM .20 Back up files rename rjava_addin.dll to OLD_rjava_addin.dll rename rjava_addinres.dll to OLD_rjava_addinres.dll rename rjavarelay.exe to OLD_rjavarelay.exe (if it exists) Double Click OM.20_hotfix12_Java_JBuilder8_02.03.2003.exe and unzip to . Follow the instructions in the \readme.txt Notes: is the directory that Rational Rose is installed in. Typically this is C:\Program Files\Rational\. The "readme.txt" file includes the following information: ---- Rational Rose Hotfix 12 for Rational Rose 2002 .20 Release PRODUCT: Rational Rose 2002 .20 Release OS: Windows CREATED: 02-03-2003 SUMMARY: Patch installation to allow for the IDE integration between Borland JBuilder 8 and Rational Rose. FIRST STEP: Unzip files. The following files will be replaced, please make a backup of each of these files. \java\rjava_addin.dll java\rjava_addinres.dll \java\rjavarelay\rjavarelay.exe (In the case where there was no integration with an IDE this file will be new) The following files will be added. \java\rjavarelay\ideLinkComponents\rjbuilderlink.jar \java\rjavarelay\ideLinkComponents\rjbuilderreceiver.dll (1) Unzip the hotfix ZIP file into the directory of the Rational products. Typically this is C:\Program Files\Rational. SECOND STEP: Register rjavarelay.exe and rjava_addin.dll (1) From an MS-DOS prompt, go to the directory of rjavarelay.exe. Typically this is C:\Program Files\Rational\Rose\java\rjavarelay. (2) Type: rjavarelay.exe /regserver (3) Go to the directory of rjava_addin.dll. Typically this is C:\Program Files\Rational\Rose\java(4) Type: regsvr32 rjava_addin.dll THIRD STEP: Run Rose and Click Detect IDE button. (1) Launch Rose. (2) Tools -> Java/J2EE -> Project Specification. Code Generation Tab. (3) Press the "Detect IDEs" Button. (4) The Log should indicate that JBUILDER 8 was detected and it is now selectable from the IDE pulldown on the Code Generation Tab. Hot Fix 13 (PNB): ----------------- Hot Fix 13 includes enhancement to Fundamental Type support, including fixes for the following defects (see attached Hot Fix 13 Release Notes). Rose J RATLC00054964 - Creating an operation with more than two parameters causes Rose to create an operation with parameters in wrong order for Remote Interface class. RATLC00212864 - User defined tags do not get refreshed for existing classes when default @tags were enabled previously. RATLC00213222 - Rose J unable to parse the reflection method properly while generating code. RATLC00235935 - Rose J Fundamental Types Enhancement (see New and Changed Features) RATLC00235936 - Rose J Enhancement to Prevent the Unloaded CAT file dialog from being displayed. In order to enable this Enhancement Request, create the following registry key entry: HKEY_CURRENT_USER\Software\Rational Software\Rose\Addins\Java\FEOnUnloadedControlUnits If registry string value is set to "Yes" - the dialog will not be displayed and instead a warning will be written to the Rose Log file. If registry string value is set to "No" - the dialog will be displayed as before (original behavior) RATLC00365313 - Wrong file format reading EJB1.1 compliant ejb-jar.xml. rose00072794 - Java code can be deleted during code generation. This defect is resolved by providing a workaround for RATLC 18283 (see below). ================================================================= * RATLC 18283 - Parent package's *.sub and or *.mdl file(s) need(s) to be write-able to generate Rose J code. Workaround Description for RATLC 18283: ================================= Rose 2002.05.20 included a new Rose J Code Generation requirement. To successfully generate Rose J code - any associated *.sub file(s) (if the *.cat files were controlled) and/or *.mdl file (if the *.cat files were not controlled) would have to be write-able. If the necessary files were not write-able, an error message would be displayed and no Rose J code generation would be performed. This new requirement was added to Rose 2002.05.20, in order to resolve: RBU 72794 - Java code may be lost during code generation, after changing Component default or custom properties. With this Hot Fix, the user may elect to disable the fix for RBU 72794. By default, the workaround for RATLC 18283 is not enabled. By enabling the workaround, the user will encounter the original Rose 2002.05.01 behavior. The user will no longer be required to have all associated *.sub and *.mdl files write-able, however, if the user changes Component default or custom properties prior to generating Rose J code and the associated *.sub and/or *.mdl files are not write-able, data loss can occur. IMPORTANT: When using this workaround, to prevent potential loss of data - one of the following MUST apply: 1. Do not change Component default or custom properties prior to Rose J Code Generation; or 2. Verify the *.sub and/or *.mdl files are write-able prior to Rose J Code Generation To Enable the RATLC 18283 Workaround - Allowing Rose J Code Generation without forcing the *.sub and/or *.mdl files to be write-able: Once this Hot Fix is installed, perform the following steps to enable the workaround for RATLC 18283: · Prior to starting Rose, run regedit · Within regedit, create the registry string value for "GenerateOnReadOnly" (if, it doesn't exist) and set this value to "Yes". (This is located under the key HKEY_LOCAL_MACHINE\\SOFTWARE\\Rational Software\\Rose\\AddIns\\Java\\) · Close regedit · Start Rose (Workaround Applied)