IBM Rational® XDE™ Modeler
IBM Rational XDE Developer - Java Platform Edition
IBM Rational XDE Developer Plus for Java Platform

Release Notes

Version 2003.06.12 Service Release

(For product upgrades)

May 2004
CT2YHNA


Copyright © 2004 IBM Corporation. All Rights Reserved.

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

Legal Notices Information


Scope

This document contains release notes for the Java editions of the IBM Rational XDE version 2003.06.12 Service Release. Because service releases are accumulative, this document also includes information about the previous, version 2003.06.01, service release. Where appropriate, material is designated as specific to a particular service release.

This release note document supplements the release notes provided with Rational XDE Version 2003.06.00 (English version) and version 2003.06.10 (Japanese version), so please refer to the appropriate base document or see the release notes for new product installations of version 2003.06.12. Some information is specific to a product package, and is designated accordingly.

Note: The printed version of this document does not include the listing of "Known Issues." In order to provide the most up-to-date information possible at release time, this information is included only in the electronic version. This document is installed with the service release, to <install-location>\Rational\doc\xde_readme_java_sr.html. You can always find the latest version at www.ibm.com/software/rational/support/documentation.

Contents

What's New in this Service Release
  In Rational XDE 2003.06.12 Service Release
  In Rational XDE 2003.06.01 Service Release
Hardware/Software Information
  Client Requirements
Installing and Upgrading
  Identifying the Package and Product Build ID
  Supported Configurations
  Installation Issues
  Upgrade Installation Information for Version 2003.06.10
  Upgrade Installation Information for Versions 2003.06.00 and 2003.06.01
License Enforcement
Compatibility Issues
  With Rational Products
Product Documentation
Restrictions and Guidelines on Using this Release
  C++
  Java
  Petal Import
  Rational XDE Extensibility (RXE)
  Web Publishing and Reporting
Defects and Changes
  Known Issues
  Defects Fixed
Contacting IBM Rational Software Support

What's New in this Service Release

The capabilities available to you in this service release depend on your packaging option. To determine the package you have installed, see Identifying the Package and Product Build ID below. For more information, see "IBM Rational Modeling Packages" in the Rational XDE Help.

In Rational XDE 2003.06.12 Service Release

This service release provides the following major enhancements for the Java platform editions:

For Java Developer and Developer Plus Editions Only

For Rational XDE Developer Plus Edition Only

In Rational XDE 2003.06.01 Service Release

The earlier Rational XDE version 2003.06.01 Service Release provided new functionality and improvements in performance and usability, including the following:

Hardware/Software Information

Client Requirements

Hardware Requirements

This release has no additional hardware requirements beyond Rational XDE Version 2003.06.00 or 2003.06.10.

Software Requirements

In Rational XDE 2003.06.12 Service Release

This service release includes new support for Windows NT 4, additonal databases, platform updates, and J2EE deployment updates. It also has changed Sun Java Plug-In recommendations.

Supported Operating Systems

The following operating systems are tested and supported: 

  • Windows NT 4 SP6a
  • Windows 2000 Professional, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
  • Windows 2000 Server, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
  • Windows 2000 Advanced Server, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
  • Windows XP Professional, Service Pack 1

Notes:

Supported Platforms
  • Rational XDE Modeler is supported as a stand-alone version that operates in a customized Eclipse shell.
  • Rational XDE Developer and Developer Plus are supported in the following development platforms:
    • WebSphere Studio Workbench 2.1.2, which is supplied during installation
    • IBM WebSphere Studio Application Developer 5.0.x and 5.1.1
    • IBM WebSphere Studio Application Developer Integration Edition 5.0
    • IBM WebSphere Studio Enterprise Developer 5.0
    • Eclipse 2.0.x and 2.1.2
J2EE Deployment
  • BEA WebLogic 5.1, 6.1, 7.0, and 8.1
  • IBM WebSphere 4.0 and 5.0
  • Sun J2EE Reference Implementation 1.3
Databases Supported

Rational XDE supports data modeling for the ANSI SQL 92 standard and the following database management systems (DBMS):

  • IBM DB2 UDB 5.2, 6.1, 7.0, and 8.0
  • IBM DB2 UDB zSeries 5.x, 6.x, and 7.x
  • IBM DB2 UDB iSeries v5 r2
  • Oracle 7.3, 8.x, and 9i for Windows NT
  • Microsoft SQL Server 6.5, 7.0, and 2000
  • Sybase Adaptive Server 12.x
Web Publishing and Reporting Web publishing requires the Java Plug-in, version 1.3.1 or later, downloadable from the Sun Web site at http://java.sun.com/products/. Publishing a model to a folder that has double-byte characters in the name requires that you use version 1.4.1_01.
Rational Unified Process and Extended Help The Rational Unified Process, or RUP, and RUP's Extended Help, requires the Sun Java Runtime Environment (JRE) plug-in, version 1.4.1, available from http://java.sun.com/products/archive/j2se/1.4.1/index.html.

In Rational XDE 2003.06.01 Service Release

This service release included modified support for Windows 2000. In addition, it included a new requirement to support Web publishing and reporting in Rational XDE Developer - Java Platform Edition.

Supported Operating Systems

The following operating systems are tested and supported: 

  • Windows 2000 Professional, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
  • Windows 2000 Server, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
  • Windows 2000 Advanced Server, Service Pack 3 or Service Pack 4 (Service Pack 4 is recommended)
  • Windows XP Professional, Service Pack 1
Web Publishing and Reporting Web publishing requires the Java Plug-in, version 1.3.1 or later, downloadable from the Sun Web site at http://java.sun.com/products/.

Installing and Upgrading

Identifying the Package and Product Build ID

To determine the package and build ID of Rational XDE that you currently have installed, run the Rational Software Installed Product Information utility by clicking Start > Programs > Rational Software > Rational Software Installed Product Information.

Rational XDE does not need to be upgraded if the build ID is listed as 2003.06.12 or higher.

Supported Configurations

This service release can be applied to the following editions of Rational XDE version 2003.06.00 and 2003.06.01:

This service release cannot be applied to the Japanese-language version of Developer - Java Platform Edition, Rational XDE version 2003.06.10. Instead, a full installation is required. See Upgrade Installation Information for Version 2003.06.10.

Do not apply this service release to any evaluation versions of Rational XDE.

Installation Issues

Upgrading Using Original Installation Method

If the original Rational product was installed from a CD image (directly to a desktop or client server), the upgrade must also be done using a CD. If the original Rational product was installed using a release area, the upgrade must be done using a newly designated release area. If the original Rational product was installed using a product download, the upgrade must also be done using a product download.

If you are unsure of the source of the original installation, the location of the installation source can be found from the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Product GUID}
The String Value named “InstallSource” contains the location of the root directory used for the installation. In the case of a CD installation, the CDROM drive will be listed. For example, with the CDROM drive mapped to drive letter E, the InstallSource String Value will contain “E:\Setup\”.

In the case of an installation from a download or a release area created through the “Enterprise Deployment” install option, the value will contain the full path to the release area or the location from where the download was extracted.

The only way to differentiate between an extracted download and a release area is through the presence of Cabinet files (extension of .cab), found in the extracted download directory. If the location listed in the InstallSource String Value contains one or more files with a .cab extension, then the source was either an extracted download, or CD content copied to the hard disk.

For more information, see defect 454398, under Installing and Upgrading.

Preparing to Install into the Eclipse Shell

This section applies to Rational XDE Developer and Developer Plus editions only. The following instructions have been updated to describe installation into an Eclipse 2.1.2 shell.

Upgrade Installation Information for Version 2003.06.10

This service release does not apply to Rational XDE version 2003.06.10 (Japanese version). In order for users of Rational XDE version 2003.06.10 to upgrade to this service release, version 2003.06.12, the following is necessary. First, uninstall Rational XDE version 2003.06.10. Then, install this service release.

To upgrade from Rational XDE version 2003.06.10 to version 2003.06.12:

  1. Read the following sections in the Rational Suite Upgrade Guide: "Removing Rational Products" and "Upgrading Desktop Systems." See link below.
  2. Back up your data.
  3. Uninstall Rational XDE v2003.06.10, and any other Rational Suite v2003.10 products.
  4. Restart your system.
  5. Install v2003.06.12 of XDE and any other Rational product.
  6. Import your saved data. To do this, refer to the Rational Suite Upgrade Guide (see "Upgrading Desktop Systems").

If needed, see Reconfiguring XDE into a Different IDE, below.

You can find the latest version of the Upgrade Guide at ftp://ftp.software.ibm.com/software/rational/docs/documentation/manuals/suite.jsp.

Upgrade Installation Information for Versions 2003.06.00 and 2003.06.01

This service release upgrades all earlier installed version 2003.06.00 and version 2003.06.01 Rational software products (this is not selectable). It will upgrade Rational XDE only if you have version 2003.06.00 or 2003.06.01. The installer will automatically detect your Rational XDE installation and configure itself accordingly.

To install the service release:

  1. Close all applications that are running, especially any version of Rational XDE.
  2. Ensure that you have administrator privileges on the system where you are installing the service release. You will not be able to complete installation if you are logged in with a userid that does not have full administrative access.
  3. Double-click the file that you downloaded. If installing from a CD, insert the CD and double-click setup.exe.
  4. Click Upgrade to bypass the welcome dialog box.
  5. Click Next in the Product Warnings dialog box after reading it.
  6. Read the License Agreement and indicate acceptance using the appropriate option button.
  7. Click Next to continue, or Cancel if you did not accept the terms of the agreement.
  8. Click Install in the Ready to Install the Program dialog box.
    Installation continues until all files and components have been copied and registered to your system.
  9. Click Finish in the Setup Complete dialog box.
  10. A reboot of your computer may be required.

You can confirm successful application of this service release by checking the build ID displayed in the Rational Software Installed Product Information dialog box. For more information, see Identifying the Package and Product Build ID.

Reconfiguring XDE into a Different IDE

In addition to applying the service release to upgrade your existing Rational XDE installation, you can also reconfigure XDE into a different IDE. For example, you can migrate your current IDE integration to version 5.1 of IBM WebSphere Studio Application Developer, or to the latest WebSphere Studio Workbench included with XDE, version 2.1.2.

There are two approaches to reconfiguring the IDE used by XDE. The more straightforward is to remove the current XDE installation and then reinstall XDE into the new IDE. The other approach is to install the service release and then use a utility that is available from Rational to reconfigure the XDE shell integration. There are more steps involved in this latter approach, but it allows ongoing reconfiguration.

Use one of the following approaches to reconfigure the shell for XDE:

Removing the Service Release

You cannot uninstall just the service release from your system. To roll back your system to a version of Rational XDE without the service release, uninstall Rational XDE, then reinstall Rational XDE

Note: If you do choose to revert to an ealier version of Rational XDE, see defect 137827 in "Known Issues," below.

License Enforcement

If you previously installed the XDE Floating License Enablement Kit, please ignore this section. License enablement of your XDE products is unaffected by this service release.

The information in this section should be reviewed by users who have purchased floating licenses for Rational XDE and require license enforcement.

When license enforcement has been activated, XDE behaves as follows:

After you configure XDE to use license keys, run the Rational License Key Administrator and point the client machine at your Rational License Server (if you have not done so already). If you do not have the license server software, you can install it from the Rational Solutions for Windows CD-Rom or download it from https://www6.software.ibm.com/reg/rational/rational-i. Refer to the IBM Rational License Management Guide on the Rational Solutions for Windows Online Documentation CD-Rom for instructions on installing and operating the Rational License Server.

Passport Advantage customers can obtain XDE license keys by referring to the "Proof of Entitlement" certificate that IBM sent you with your XDE product purchase. If you are not a Passport Advantage customer, you can obtain your XDE license keys from your local IBM Rational Sales Representative or from Customer Service.

Compatibility Issues

With Rational Products

Rational XDE with Rational PurifyPlus

Rational XDE with Rational SoDA

Product Documentation

For information about accessing the online Help provided with Rational XDE, please see "Getting Started" in the Rational XDE Version 2003.06.12 Release Notes for new product installations.

Restrictions and Guidelines on Using this Release

C++ (for XDE 2003.06.12 Service Release)

Changing the Default Text Editor for Viewing and Modifying Code

Rational XDE is installed with several text editors that have varying capabilities and interfaces. This selection of editors gives the user a great deal of choice in how to view and edit code. 

To change the default editor

  1. On the Window menu, click Preferences.
  2. Expand Workbench, and then click File Associations.
  3. Under File types, click the file type for which the editor binding is to be changed.

    Note that you can also click the Add button to add a file type that is not listed.

  4. Under Associated editors, use the Add, Remove, and Default buttons to modify the editor associated with that file type.
  5. Click OK.

Importing Rational Rose ANSI C++ Models into Rational XDE

Rational Rose ANSI C++ models can be imported to Rational XDE. Additional infomation on importing Rose models into XDE can be found in the online Help installed with XDE. Also, please see defect 245970 below about adjusting class sizes in the diagram window after importing.

XDE and Rose Concepts

XDE works differently from Rose in a number of ways, but the most relevant are:

File Locations

XDE requires that new files be created in a directory below the project root. For instance, if you create an XDE C++ modeling project in the directory C:\myproject, new files are then created below the myproject directory.

When importing a Rose model into XDE, it is recommended that the XDE project be created in a directory that contains all the Rose source code in order to fully take advantage of the XDE product's code-browsing features. For example, if the Rose project uses source code in the directories C:\rose-project\juniper and C:\rose-project\yew, then the XDE project should be created in C:\rose-project.

Project Constraints

It is essential that XDE projects not overlap. An XDE project contains references to all file resources in the directory tree below its location (the project root). XDE does not allow multiple projects to contain references to the same resource.

You cannot have two XDE projects in the same project root. You can also not have a project in a subdirectory of another project's root directory. 

Multilanguage Projects

Rose supports projects with multiple implementation languages; that is, multiple language classes can coexist in one Rose model. If this type of model is imported to a C++ project, all the classes are converted to the C++ code model, but the Synchronize property for non-C++ classes is set to Excluded so that they do not participate in round-trip engineering.

Java (for XDE 2003.06.12 Service Release)

The Java/J2SE add-in does not currently support round-trip engineering of Java files that are "linked resources"—that is, .java, .class, or .jar files that are themselves defined as linked resources, resources that are outside the project itself but referenced through the linked resource path variables, or resources that are contained within a folder that is a linked resource.

Petal Import (for XDE 2003.06.01 Service Release)

In the earlier service release, you can only open petal model files created using versions of Rational Rose up to version 8.0. In order to import petal model files created using Rose version 8.1 in this service release, use the Save As functionality in Rose to save the version 8.1 petal model file as Rose version 8.0. Once the petal model file is saved to a previous version of Rose, the file can then be opened with this release of XDE. (This is not an issue in Rational XDE 2003.06.12 Service Release.)

Rational XDE Extensibility (RXE) (for XDE 2003.06.12 Service Release)

Web Publishing and Reporting (for XDE 2003.06.01 Service Release)

The Rational XDE 2003.06.01 Service Release added Web publishing and reporting capabilty for the Rational XDE Developer - Java Platform Edition. The restrictions and guidelines listed in the release notes for Rational XDE 2003.06.00 also applied to these users. For more information, see Rational XDE Version 2003.06.12 Release Notes for new product installations.

Defects and Changes

Known Issues

The following tables describe the known issues in this and previous service releases.

In Rational XDE 2003.06.12 Service Release

Category

ID

Description

C++
245816
You may be unable to close the C++: Add Source files dialog box because of a reappearing error message dialog box. This happens if you click the Add Files button and enter a nonexistent directory name, and then click the Add Recursive button.

Workaround: The C++ Add Source files dialog box can always be closed by pressing the ESC key.

Configuration Management
245044

Rational XDE customers who have installed recent ClearCase v2002.05.00 Windows patches (for example, patch 24 and 26) will start receiving prompts to reinstall the XDE/ClearCase Type Manager Installer. This is due to the ClearCase patch overwriting the XDE bindings in ClearCase control files that steer compare and merge operations to the XDE compare/merge facility.

Workaround: Uninstall and then perform a reinstall of the XDE/ClearCase Type Manager Installer on the server and on the client. This will have to be repeated after every ClearCase patch install. Monitor future ClearCase patches for fixes for this issue. XDE customers who also use the WebSphere Studio Application Developer 5.1.x UML Diagramming feature should contact IBM Rational Customer Support for assistance.

246156

It is possible for newer versions of a model to be loaded during a rebase, update, or deliver operation; therefore, we recommend that the user do the following when performing one of these operations:

  1. Save any unsaved changes.
  2. Perform the operation (rebase, update, or deliver).
  3. In the Model Explorer, click the Reload All Models button.
Data Modeler
244321

After you use Petal Import to open an existing Rose model in Rational XDE, you must do the following:

  1. Reset the data model default database target.
  2. Reset the domain database target.
  3. Assign the domain package to the data model using a dependency relationship.
244285

The many-to-many relationship tool does not correctly resolve table names that contain apostrophes ( ' ).

Workaround: Remove the apostrophes or create the relationship manually.

To create a many-to-many relationship manually:

  1. In a diagram, add the tables that participate in the many-to-many relationship.
  2. On the Data Modeler tab of the Toolbox, click the Table tool, and then click the diagram that contains your many-to-many relationship tables. The new table created is your intersection table.
  3. Add an identifying relationship between each of your many-to-many relationship tables and the intersection table. The intersection table must be the child table of each identifying relationship.
  4. Set the multiplicity of each identifying relationship to 1..*
244364

Additional DB2 templates are visible when creating a DB2 UDB zSeries data model.

Workaround: Select only the templates titled "DB2 zSeries." The other templates (MVS) are for those with data models from previous versions of Rational XDE.

244570

DB2 UDB zSeries large tablespaces cannot be reverse-engineered or generated to a database or DDL file.

244568

Rational XDE data modeling offers limited support of DB2 UDB zSeries version 8; i.e. only version 7 elements and statements are supported.

To use DB2 UDB zSeries version 8 in a data model, you must use the DB2 UDB zSeries v6 & v7 database target in the engineering wizards and the database default.

This support is based on pre-GA DB2 UDB zSeries version 8.

244557

When you reverse engineer DB2 UDB zSeries functions, the return type defaults to smallint.

Workaround: Reset your return type after the reverse engineering process is complete.

244453

When reverse engineering DB2 UDB zSeries from the database, the tablespace erase rule does not reverse engineer.

Workaround: Set the tablespace erase rule using the IsErase property. Set this property to True for ERASE YES, or set it to False for ERASE NO.

244569

Columns that use computed columns as a default value receive an unresolved identifier error when validating a data model. This is not a valid error.

Workaround: Ignore the error.

244555

A view dependent on another view is reverse engineered from the database as a user-defined view, so a dependency relationship between the views is not created.

244571

When you reverse engineer DB2 UDB zSeries nullable columns from the database, Rational XDE assigns a Null default value to the column.

Workaround: To preserve your column syntax when you generate to a DDL file or database, remove the Null default value from the column.

245539

If you remove a pk/fk from a table, and attempt to export the entire table to a DDL file using Compare and Sync without validating the model, then you will recieve an ArrayOutofBoundsException error. If you encounter this error you must restart XDE.

Workaround: Validate the model (as recommended in the best practices) and fix the invalid relationship before proceeding with Compare and Sync.

245839

WSSAD 5.0.1. If you created a DB2 UDB data model in Rational XDE 2003.06.01 Service Release, and then upgraded to the XDE 2003.06.12 Service Release, XDE may not respond when you attempt to open a Specification dialog box for DB2 UDB database elements created prior to the upgrade. This is due to incorrect identifier lengths or an incorrect maximum identifier length default. If XDE stops responding you must restart XDE.

Workaround: In XDE 2003.06.12 Service Release, reset the Data Modeler Database Defaults preference to increase the maximum identifier length, or shorten the length of the existing identifiers within the model.

245889

The Rational XDE Help for Data Modeler should include the following information: When performing multiple transformations of the logical data model to a data model you can re-transform your logical data model to different data model packages for each transformation. If you want to re-transform your logical data model to the same data model package for every transformation, you must be aware that XDE does not:

  • Synchronize between the logical data model and the data model. If you deleted elements in the logical data model, those elements are not deleted in the data model.
  • Generate indexes for foreign keys, even if you specify that in the class to table transformation dialog box.
  • Generate some constraint names correctly.
Documentation
243667
The Javadoc version of the RXE API documentation does not reflect the inheritance model used in the Patterns and Code Templates portion of the API. The actual inheritance used is as follows (indentation indicates inheritance.)
  • IRXEPatCTCalloutData
    • IRXECodeTemplatesExpansionData
    • IRXEPatCalloutData
      • IRXEPatVetoableCalloutData
        • IRXEPatternsOnArgumentValueCalloutData
        • IRXEPatternsOnBindCalloutData
        • IRXEPatternsOptionalElementCalloutData
        • IRXEPatternsWizardCleanUpCalloutData
        • IRXEPatternsWizardStartUpCalloutData
        • IRXEPatternsExpansionLocationCalloutData
      • IRXEPatAbortableCalloutData
        • IRXEPatExpansionCalloutData
          • IRXEPatternsPreExpandCalloutData
          • IRXEPatternsPostExpandCalloutData
        • IRXEPatternsPreApplyCalloutData
        • IRXEPatternsPostApplyCalloutData
        • IRXEPatternsErrorCalloutData
        • IRXEPatternsPostMappingCalloutData
        • IRXEPatternsCollectionCalloutData
      • IRXEPatElementCalloutData
        • IRXEPatternsMergeCalloutData
        • IRXEPatternsMatchCalloutData
        • IRXEPatternsScriptletCalloutData
  • IRXEPatApplicationMap
  • IRXEPatExpansionMap
  • IRXEPatCTCalloutUser
    • IRXECodeTemplatesExpansion
    • IRXEPatternsCallout
  • RXEPatCTArgumentTypes
  • RXEPatApplicationEvents
  • RXEPatNextOptions
  • RXEPatElementMergeBehaviors
245889
See the description for defect 245889 above, in the "Data Modeler" section of this table.
246175

See the description for defect 246175 below, in the "General XDE" section of this table.

375451
The Help for Visual Trace should include the following text: "You must engage Visual Trace before starting the application to be traced."
453915

In Rational XDE Help, an incorrect description is included in the topic “Defining Code Template Bodies.”

Workaround: In this topic, within the "For a Body Kind of Java" section, the interface name IRXECTCallOutUser should be replaced with IRXECodeTemplatesExpansion.

Installing and Uninstalling
137437

When installing into IBM WebSphere Studio Application Developer version 5.1.1, it may be necessary to upgrade the underlying Java Runtime Environment (JRE).

To determine whether an upgrade is necessary after installing this service release, you must check the two build identification numbers associated with the JRE within WebSphere Studio Application Developer.

  • Find the first number by running the following command, where <WS_JRE_Path> is the path to the JRE directory within Application Developer: <WS_JRE_Path>\bin\java.exe -version
    The JRE version information is returned, and the build identification number is included.
  • Find the second number by running the following command:
    < WS_JRE_Path>\bin\java.exe -Xj9 -version
    The J9 version informaiton is returned, and the build identification number is included.

You do not need to upgrade the JRE if the following versions are returned:

  • JRE build identification number: 20031021
  • J9 component build identification number: 20031201

If you see any other numbers, then the JRE was not upgraded and you must do the upgrade manually.

Note: The WebSphere JRE will be upgraded during installation of this service release if the JRE build number is 20031021 and the J9 component build number is 20031021 or 20031103. The JRE build number does not change when upgraded.

Workaround: Manually upgrade the JRE by manually copying the following directory to the jre directory within WebSphere Studio Application Developer 5.1.1:
<XDE-install-location>\Rational\Common\XDE_WSAD_JRE_UPDATE\jre

This directory includes all the files required to upgrade the JRE.

137827

If you uninstall Rational XDE version 2003.06.12, two DLLs may be removed that are required but not reinstalled if you install another version of XDE, including version 2003.06.00 and 2003.06.10. These two required two DLLs, msvcr71.dll and msvcp71.dll, can be reinstalled once uninstallation is complete. To determine whether these DLLs are missing, look in the system directory, typically, C:\Windows\System32. Also, if these files are missing, you may see the following error message when opening a diagram in a model:

"An error occurred in IRSWindowPane::CreatePane() during opening a document window"

Workaround: To learn more about obtaining, reinstalling, and registering the deleted DLLs, contact IBM Rational Customer Support.

242345

Under Windows NT, XDE may fail to install into WebSphere Studio Application Developer 5.0.1 if the value for the NT 4 registry size is less than 40.

Workaround: Set the NT 4 registry size to 41 or more: Right-click My Computer, click Properties, click the Performance tab, click Change under Virtual Memory, and set Maximum Registry Size to 41 or greater.

454398

When upgrading from a previous 2003 version of an IBM Rational product using the 2003.06.12 CDs, the following message may continue to display with Disk 1 in the CD drive: “Please insert the disk: Disk 1”

This happens when the original installation was performed using a designated release area created through the "Enterprise Deployment" install option, or for a product that was downloaded from the Web.

Workaround: Read the related technical note. Go to www.ibm.com/software/rational/support/ and search for the text "upgrade insert disk 1.”

Internationalization
237570

The default font used on the drawing surface is not suitable for all languages (especially Asian languages).

Workaround: Users should change the default font face in the Preferences dialog box (on the Windows menu) by expanding Rational XDE and Appearance, and then clicking General. Choose a font that supports your character set. Also, select Default for new models in the Settings for list to ensure that the change applies to all new models.

245756

An English-language error message appears when starting the Rational Unified Process, or RUP, and RUP's Extended Help, if you have not installed the Sun Java Runtime Environment (JRE) plug-in, version 1.4.1, for your Web browser. For a workaround, see defect 245756 under "General XDE."

453121

If a file is updated during code generation, a space is appended to the end of the file for each Japanese character in the file. This happens every time the file is updated on code generation.

Workaround: Remove spaces at the end of the files that were updated during code generation.

453933
The XDE-supplied file RASRepositoryService-portable.war, provided as part of the J2EE RAS Repository, does not support internationalization requirements. When you create a J2EE-type repository service with this file, any Japanese characters in the assets owned by the repository will display as question marks (?) in XDE.
593705

Publishing a model to a folder that has double-byte characters in the name causes the tree control to fail in the published model.

Workaround: Replace the default Sun Java Runtime Environment (JRE) version 1.3x with version 1.4.1_01.

Java
245085

If two packages contain a class with the same name and you attempt to move one of the classes into the package with the conflicting class by changing its package statement and then synchronizing (or if you perform this change with autosync enabled), the move of the class will fail. At the point of failure, the output log will indicate that there was a failure to rename the class. The Model Explorer will then show a new class and component with "_1" appended to the name. In addition, you will see a component with "_1" appended after ".java".

For example, if a class is named ClassA and its corresponding component is ClassA.java, you will see ClassA_1 and two new components, ClassA_1.java and ClassA.java_1. The class ClassA_1and component ClassA_1.java will have no corresponding file on disk. Attempting to browse code on these will result in an error message indicating that the source file could not be located. The component ClassA.java_1 will point to the renamed class source file, which remains in the original packages directory on disk since it could not be moved.

Workaround: Use the following steps with autosync enabled:

  1. In the Navigator, rename the source file in the original package to match the new name. In the example above, that would be ClassA_1.java.
  2. Drag the renamed file from step 1 into the new package.
J2EE
243758

When using Rational XDE with IBM WebSphere Studio Application Developer 5.0.x and synchronizing a Run As security role in the EJB deployment model, the role is not updated in Application Developer.

Workaround: Assign the role in the <run-as> deployment descriptor entry in the Application Developer editor.

243880
When the web.xml file declares more than one filter URL pattern and the file is externally modified to delete a URL filter pattern, the tag editor does not update the file correctly. The web.xml file is invalid because an empty tag exists representing the deleted filter URL pattern. The errors occurs on reimporting the modified web.xml file.

Workaround: In the Web deployment model, select the servlet filter with the externally removed Web filter URL pattern. Then, in the Properties window, open the tag editor for the WebFilterURLPattern property, click OK, and close the tag editor. This triggers the system to clean up the blank Web filter URL pattern.

243962

The deployment descriptor editor for IBM WebSphere Studio Application Developer does not always refresh immediately after a Rational XDE-Application Developer synchronization. As a result, changes made from XDE may not be visible in Application Developer until the user closes and reopens the editor. For example, when a CMP field is added to an Entity Bean in XDE, the new CMP field is shown in the J2EE hierarchy, but not the CMP field section of the Bean tab.

Workaround: Close and reopen the editor.

RXE
243418
The RXEMenuExtender target tag <AppendSelection> currently appends only the specific elements selected. It will not append a grouped set of elements.
244437
If a model is opened in RXE via a program called by the Menu Extender before the Model Explorer has initialized, the model will appear in the Model Explorer only if a write action has been opened prior to opening the model. If either a read action or no action is open, the model will not appear in the Model Explorer.
244495
If a model is closed by a program called by the Menu Extender, it will still appear within the Model Explorer.
244507
The Menu Extender samples referenced in the documentation, including the appropriate target programs, are stored in C:\Program Files\Rational\XDE\Addins\RXEMenuExtender\examples. This path is subject to change depending on your installation location.
244508
IRXEDiagram.renderImage( ) does not support the .GIF format in this release.
244560
RXE scripts run from a menu that create and save models to a configuration-management-controlled directory will not be added to the configuration management system under the .NET shell. These models will only be added to the configuration management system under the Eclipse shell.
Visual Trace
135408

The IBM Java Runtime Environment (JRE) that ships with the IBM WebSphere Studio Application Developer platforms prior to version 5.1 does not provide the ability to use Visual Trace when running in debug mode. As a result, users of the Rational XDE Developer Plus for Java Platform Edition who engage Visual Trace will not produce a trace sequence diagram when J2SE applications are run in debug mode.

Workaround: An updated version of the JRE is included with the XDE product media. For installation instructions, see the related "Installation Issues" note above. Alternatively, you can upgrade to Eclipse version 2.1 or WebSphere Studio Application Developer version 5.1.

137862
IBM WebSphere Studio Application Developer crashes when IBM Rational XDE is being used to try to display a sequence diagram from a trace of an application that contains a very long method signature of more than 1,000 characters.
375451
See Documentation defect above, 375451.
Web Publishing and Reporting
243697

If you filter out a particular element type (such as Text), hot spots that have no associated links may be created in the published model.

Workaround: Remove all filters before publishing a model.

245328
If you try to publish a model without having the Java Runtime Environment (JRE) installed, XDE displays a message that prompts you to install the 1.3.1 release of Java Plug-in Software. After installing Java Plug-in 1.3.1, when you try to publish a model, XDE displays the following error message:

Java(TM) Plug-in 1.4 Fatal Error
Java Plug-in 1.3.1 cannot be located because values in the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Java Plug-in\1.3.1 is not found or is no longer valid.

Workaround: Install the 1.4 release of Java Plug-in Software before or after installing XDE.

374690
If you publish a model that includes global actions, those actions are not represented in the published model.
375379
If you are linking an external file to a model element, you can specify the file reference for the link with either an absolute path or a relative path. File references that are specified with relative paths do not publish to the Web correctly.

Workaround: If you want to publish a model to the Web, specify only absolute paths for all linked files.

To specify an absolute path for a linked external file, do the following:

  1. In the Model Explorer, right-click the model element to which you want to link an external file, and then click Add UML > URL.
  2. In the URL Input Dialog dialog box, clear the Use relative path representation for all file references check box.
  3. Click Browse, browse to and select the file that you want to link to the model element, and then click Open.
  4. Click OK in the URL Input Dialog dialog box.
General XDE
44806

When you open a dialog box to browse to a folder in IBM WebSphere Studio Workbench on Windows NT 4, the dialog box may lose focus and be obscured by other dialog boxes.

Workaround: Use Alt + Tab change focus or click the desired dialog box. This a known issue for Eclipse running on Windows NT.

241325
During the model upgrade process (especially with non-US English models), the XDE print preferences may not upgrade correctly.

Workaround: After the model upgrade process is complete, click Window > Preferences, and then expand Rational XDE > Print. Click Page Setup and click the Restore Default Settings button. Verify that all numeric values are compatible with your local metric system and that all values are correct for the current model, all default preferences, and the print preferences for individual diagrams.

241771

Users who have installed Rational XDE Developer Plus on Windows NT may find that saving a blank model assigns a Rational RequisitePro applied profile to the model.

Workaround: Manually reset the model's Applied Profile property to Blank.

243239

When you export a Rational XDE model using the XML Metadata Interchange (XMI) file format, the following harmless error messages may appear if the ClassicRose profile is applied to the model you are trying to export and the model contains XDE-created realization and abstraction relationships:

  • Tagged value "ClassicRose::Visibility" not found for element "xx_Abstraction"
  • Tagged value "ClassicRose::Friend" not found for element "xx_Abstraction"
  • Tagged value "ClassicRose::MultiplicityTo" not found for element "xx_Abstraction"
  • Tagged value "ClassicRose::MultiplicityFrom" not found for element "xx_Abstraction"

The error messages appear because there is no UML:Realization metaclass in UML/XMI. On XMI export, Rational XDE realizations and abstractions stereotyped as "Realize" are exported as UML:Abstraction stereotyped as "Realize". On XMI import back into Rational XDE, all abstractions with “Realize” stereotypes become realization relationships in XDE.

244103
If you click a class shape in the diagram window, then click the diagram surface and click a class shape again, the check marks displayed in the Show/Hide Compartment list on the Appearance toolbar do not update to show which compartments are currently visible on the last class shape selection.

Workaround: Change the selection directly from one class shape to another class shape to display the correct settings or select another class shape and then reselect the desired shape to update the list.

244643, 244687

When you export a Rational XDE model to the Unisys 1.3.5 file format, multiple state and final state actions (such as do, exit, and entry) are not exported. When you import the Unisys 1.3.5 file back into XDE, only one action (a do action) is imported. All actions (UninterpretedActions) should export and import correctly.

Workaround: Remove multiple actions that reside within an activity model element before exporting a model in the Unisys 1.3.5 format.

244776
You can add multiple events such as signals, calls, and time events to a transition in Rational XDE. However, when you export an XDE model that contains transitions with multiple events to the Unisys 1.3.5 XMI file format, you cannot import the same model back into XDE.

Workaround: Add one event per transition when you want to associate multiple events with a transition.

245150
If you export a Change Event model element with the Change property assigned to a specific string, the export representation generated in the XMI file is incorrect. The attribute "body" is generated twice, which causes the exported result to be incorrect syntatically.

Workaround: Change the duplicate attribute "body=" to "language=" in the exported XMI file.

245197

If you are running Windows 2000 and have installed the Japanese version of this service release into the IBM WebSphere Studio Application Developer version 5.1.1 shell, the Help window may become corrupted or hang if you switch between the Help window and other windows.

Workaround: Close the Help window and restart the shell. The next time you use Help, it will work normally.

245408

Associating one constraint with multiple model elements causes XDE to hang during an XMI import.

Workaround: Only associate one constraint with one model element.

245427
Activity graphs with a SubactivityState reference export to an XMI file format correctly; however, when you import the XMI file back into XDE, the reference is not interpreted correctly. The imported model will not have an ActivityGraph reference for a SubactivityState. There is no workaround for this defect.
245430
Object Flow States with a Classifier reference export to an XMI file format correctly; however, when you import the XMI file back into XDE, the reference is not interpreted correctly. The imported model will not have a Classifier reference for an Object Flow State. There is no workaround for this defect.
245432
Call Events with an operation reference export to an XMI file format correctly; however, when you import the XMI file back into XDE, the reference is not interpreted correctly. The imported model will not have a operation reference for a call event. There is no workaround for this defect.
245756

The Rational Unified Process, or RUP, and RUP's Extended Help, will not work if you have not installed the Sun Java Runtime Environment (JRE) plug-in, version 1.4.1, for your Web browser. In addition, the related error message appears in English and is not localized.

Workaround: Install Sun JRE 1.4.1.

To install the JRE plug-in, do one of the following:

  • If you have installed RUP from a CD, you can execute the JRE plug-in installer from the Rational common directory:
    [INSTALLDIR]\common\rwp\JRE_plugins\j2re-1_4_1-windows-i586-i.exe
    where [INSTALLDIR] is the installed Rational products directory. For example,
    C:\Program Files\Rational.
  • Download and install the JRE from the Sun Java Web site, using this link:
    http://java.sun.com/products/archive/j2se/1.4.1/index.html

For other options, please contact your organization's technical support staff.

When finished installing, restart RUP or Extended Help.

245970

When you import a model file from Rational Rose into Rational XDE, classes that have stereotypes may become very large in the diagram window.

Workaround: After importing, click Format > Automatic Resize or manually resize the class to a desired shape.

246137

After you use Rational SoDA to generate a report on an XDE model, you may be unable to open diagrams in XDE and you may see a variety of error messages.

Workaround: To resolve this issue, completely close SoDa, including the report, the template, and the Document2 document. To compare the report to the model, relaunch SoDA and reopen the report.

246175

If you are running Rational XDE on Microsoft Windows NT, you may see the following error message when attempting to launch Extended Help from the Help menu: "Extended Help is currently not available."

Workaround: You need to add the following Windows registry keys to use Rational Unified Process Extended Help:

Registry Key Name: HKEY_CLASSES_ROOT\htmlfile\shell\opennew

  • Name - (Default)
  • Type - REG_SZ
  • Data - &Open

Registry Key Name: HKEY_CLASSES_ROOT\htmlfile\shell\opennew\command

  • Name - (Default)
  • Type - REG_SZ
  • Data - "C:\Program Files\Internet Explorer\iexplore.exe" %1

Note: The data for the HKEY_CLASSES_ROOT\htmlfile\shell\opennew\command registry key needs to be based on the data for the HKEY_CLASSES_ROOT\htmlfile\shell\open\command registry key. This will allow you to launch the Rational Unified Process Extended Help with your default browser.

518939
If you are using Rational XDE installed into Eclipse 2.0, you may see the following issue. A redundant Save As dialog box appears when you save a model with the focus set on the diagram window.

Workaround: You can safely ignore the redundant Save As dialog box by clicking the Cancel button. The model is saved correctly.

In Rational XDE 2003.06.01 Service Release

Note that the Web publishing and reporting issues now apply to all Java platform editions in the Rational XDE 2003.06.01 Service Release.

Category

ID

Description

Data Modeler
241752

Creating new triggers for a table or view will cause an exception if the name of the respective table or view is less than 3 characters in length.

Workaround: When adding a new trigger for a table or view, ensure that the name of the corresponding table or view is at least 3 characters long.

Internationalization
595383, (82143)
This defect now applies to all Java platform editions. When downloading the Java plug-in required for Web publishing, if you are running a Japanese operating system, you must choose the International version of JRE from the Sun Web site (for Netscape) or select the appropriate Locale (for Internet Explorer). See defect 591378 for information on the Java plug-in requirement.
Web Publishing and Reporting
(71502), (79902), (85797), (85867), 591378, 594158, 597257, 597295
The publishing function requires the Java Plug-in. The Java Plug-in is not included in the Rational XDE installation. If you attempt to use the publishing capability before you have the plug-in, one of these will happen:
  • The Java Plug-in installation wizard starts and leads you through the installation process. (Internet Explorer)
  • You are connected to the Sun Web site to download the Java Plug-in. (Netscape Navigator) 

Workaround: Download the Java Plug-in from the Sun Web site, http://java.sun.com/products,  before you use the publishing/reporting capabilities.

Although the applet is signed by Rational, it could happen that the default security settings for the Java Plug-in version 1.4 do not allow read permission. Workaround: See the instructions under Restrictions and Guidelines on Using this Release, Web Publishing and Reporting.

(84246), (86198), 596528, 597457

A model element name that contains an single quote (‘) is truncated at that single quote in the published model tree.

Workaround: Do not use a single quote in a model element name.

(85508) , 597125

You cannot display published models using UNC paths. The Java tree will not load as expected.

Workaround: Map a network drive to the remote machine to view it from a remote system or copy the published model to a local machine to view it locally.

(85176), (86419) , 596972, 597557

In rare cases, when you publish multiple models successively, you may get the following message, which prevents you from performing any further actions in the model: "A read action is open on behalf of client ‘RSE Client’."

Workaround: Exit and restart Rational XDE.

(87286), (87521) , 597948, 598061

The Getting Started sample model file may not publish completely when published more than once during the same Rational XDE session.

Workaround: If you want to publish the Getting Started model a second time, close and reopen Rational XDE to create a new session.

(87337), (87519) , 597968, 598060

If a user name contains an extended character, a path error occurs. This prevents successful publishing and reporting of models and results in the following message: "ParameterFile.txt\ProjectConsole.ini does not exist."

Workaround: In your user directory, there are two folders based on such a user name: one with the extended character presented correctly (for example: Administratör) and one with the extended character presented incorrectly (for example: Administratör). Copy the ProjectConsole.ini file from the incorrectly named folder to the correct folder.

(87410), (87819) , 598009, 598224
Hotspots are created in Generated Reports as well as in Published sites. These report hot spots are incorrect and link to nonexistent files. The generated report will, however, display and print correctly.
(87752), (87858), 598186, 598244
Hotspots are currently not supported on activities contained within swimlanes.
241330

If you are using an installation of Rational XDE that was installed by another user, you may be prompted to install additional components when you attempt to publish a model. The suggested installation is unnecessary; you should click Cancel. Publishing will then proceed normally.

If you allow the process to finish by not clicking Cancel, a second dialog box appears that suggests a restart. You should click No. If you click OK, XDE restarts and the published model is incomplete.

372979

In a published model, displays that rely on a relationship with a MessageEnd object fail. These failures include:

  • A sender/receiver table.
  • Sequence elements in a sequence diagram that contains a reference between an operation and a message.
373221

If you have installed both Rational Suites and Rational XDE, uninstalling either product will result in failed graphics support for reporting, including diagrams.

Workaround: Reinstalling the product that was removed will resolve this limitation.

374053

If you use Netscape 6.0 as your default browser, and you generate a report or publish a model with the option to "open ... upon completion," Netscape opens behind other windows.

Workaround: Bring the Netscape window to the front by clicking in the status line or by using Alt+Tab. Alternatively, set Internet Explorer as your default browser.

General XDE
242670

The product version number displayed in the About Rational XDE Features dialog box shows "2003.06.00" instead of the Service Release 1 version number, "2003.06.01." You see this by clicking Help > About Rational XDE, clicking the Feature Details button, and then clicking the Rational XDE feature row.

Please reference the version information provided by the Rational Software Installed Product Information utility.

Defects Fixed

The following tables describe the defects fixed in this and previous service releases.

In Rational XDE 2003.06.12 Service Release

Category

ID

Description

Data Modeler
241752

Creating new triggers for a table or view will cause an exception if the name of the respective table or view is less than 3 characters in length.

Workaround: When adding a new trigger for a table or view, ensure that the name of the corresponding table or view is at least 3 characters long.

Documentation
242208

The online Help for Data Modeling states that you can assign a domain to an attribute in a logical data model. This functionality is not supported.

RXE (Patterns and Code Templates)
51339

The operation getRXE() fails in the Visual Basic PreExpand callout. It may also fail in other Visual Basic RXE callouts.

51437

In pattern callouts related to the use of the Apply Pattern Wizard and Apply Pattern dialog box, the
RXE’s getRXE() method does not return the correct value. This method is used to acquire the
RXE application that can be used, for example, to write to the Output window.

134788

Unable to successfully query for the Type value of the CTArgumentValue in a pattern callout so the callout fails.

134973

A pattern’s template parameters can have both a collection value source and a user value source. Patterns with both value sources and only user argument values (no collection values are generated), cause a callout’s RXE lookupParameterValues() method to incorrectly return null. Expected return is an array of CTArgumentValueHolders containing the user-entered values.

135069

 

In the Patterns OnBind callout, getThisElement() should return the pattern template because that is the element to which the OnBind callout is attached (the pattern template "owns" the onBind callout). Unfortunately, getThisElement() is returning the model in which the bound collaboration (pattern instance) is located.

Visual Trace
241144
Visual Trace will cause Rational XDE to terminate at the start of a debug/run session if XDE is installed into a directory that contains Japanese or double-byte characters in the name.

447942

Visual Trace is not always able to differentiate between applications launched by a user and other processes started as a result of an IDE action. This can result in Visual Trace attempting to trace processes unintentionally and displaying the following warning: "Visual Trace supports only tracing one application at a time. Please stop all other applications being traced and restart the application."

514577

The following defect is now associated with solution 187450534. Please refer to this number when calling technical support for additional information.

Visual Trace uses a socket to connect to the application being traced. If a connection cannot be established, the following warning is displayed: "Visual Trace could not establish a socket connection with target."

In Rational XDE 2003.06.01 Service Release

Category

ID

Description

RequisitePro Integration
59126, 238444
Using the Rational RequisitePro-XDE integration caused JVM error messages when closing Rational XDE.
RXE
240020, 240024

The RXE documentation for Rational XDE Developer - Java Platform Edition is now more complete and includes the following:

  • "Extracting Properties Shown in the Property Editor" topic
  • Correct introductory paragraph for the "Java Sample" topic
  • Additional paragraph appended to the "Converting RXE Objects Between Types" topic

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 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 www.ibm.com/software/support.