IBM Rational XDE Modeler - .NET
IBM Rational XDE Developer - .NET Edition
IBM Rational XDE Developer Plus for .NET

Release Notes

Version 2003.06.15 Service Release, August 2005

(For product upgrades)

8/1/2005
GI11-4685-05


Copyright © IBM Corporation 2002, 2005. 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 Microsoft .NET editions of the IBM Rational® XDE™ Version 2003.06.15 Service Release. Because service releases are accumulative, this document also includes information about the previous service releases, versions 2003.06.01, 2003.06.12, 2003.06.13, and 2003.06.14. 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, so please refer to that document or see the release notes for new product installations of version 2003.06.15, available from the IBM Publications Center (see the note below).

Note: This document was accurate at the time this product was prepared for release. The most recent version of this file is available in the IBM Publications Center at www.ibm.com/shop/publications/order. (To search for the IBM Publications Center, go to www.ibm.com and enter "IBM Publications Center" in the Search field.)

Some information is specific to a product package, and is designated accordingly.

Additional updates may be available for this service release. To determine if there is an update that applies to this release, take the following steps:

  1. Browse to the Downloads and Drivers page, at http://www.ibm.com/support/us/all_download_drivers.html.
  2. Enter "XDE" in the Search field and select Updates in the Download Type field.
  3. Click Submit.
  4. Review the results list.

Contents

What's New in this Release
  In Rational XDE 2003.06.15 Service Release
  In Rational XDE 2003.06.14 Service Release
  In Rational XDE 2003.06.13 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
License Enforcement
Compatibility Issues
  With Rational Products
Product Documentation
  Help Behavior
  Data Modeling
  Modeling
  Round-Trip Engineering
  Web Publishing
Restrictions and Guidelines on Using this Release
  Data Modeling
  Petal Import
  Rational XDE Extensibility (RXE)
Defects and Changes
  Known Issues
  Defects Fixed
Contacting IBM Rational Software Support

What's New in this 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.15 Service Release

This service release provides support for multiple-model publishing and bug fixes for the .NET platform editions.

In Rational XDE 2003.06.14 Service Release

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

In Rational XDE 2003.06.13 Service Release

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

Note: IBM Rational v2003.06.13 products do not officially support Windows XP Professional, SP2, and the information in this document is based on testing done with a Windows XP SP2 release candidate. The production release of Windows XP SP2 was not available for final testing at the time this document was finalized. Contact IBM Rational Software Support to obtain the latest information on Windows XP SP2 support.

In Rational XDE 2003.06.12 Service Release

The earlier Rational XDE 2003.06.12 service release provided the following major enhancements for the .NET platform editions:

For .NET Developer and Developer Plus Editions Only

In Rational XDE 2003.06.01 Service Release

The earlier Rational XDE version 2003.06.01 Service Release provided improved 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.

Software Requirements

This service release includes no new software requirements.

Previously, the Rational XDE Version 2003.06.13 Service Release included full support for Microsoft Windows XP Professional, Service Pack 2, and clarified support for Windows 2000 service packs. The Rational XDE Version 2003.06.13 Service Release included expanded Windows XP Professional support. The Rational XDE Version 2003.06.12 Service Release included new support for Windows NT 4 and expanded database support. It also recommended upgrading to Sun Java Runtime Environment (JRE) plug-in version 1.4.1. The earlier Rational XDE Version 2003.06.01 Service Release added support for Windows 2000 SP4. There are no other changes in software requirements beyond Rational XDE Version 2003.06.00.

Supported Operating Systems

The following operating systems are tested and supported: 

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

Notes:

  • Windows NT is not a supported operating system for Visual Studio .NET 2003.
  • Visual Studio .NET 2003 requires Windows 2000, Service Pack 3 or later, or Windows XP Professional.
  • See note under Installation Issues below about Windows XP, Service Pack 1.
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.

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.15 or later.

Supported Configurations

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

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

Installation Issues

General

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

Upgrade Installation Information

This service release upgrades all installed version 2003.06.00, 2003.06.01, 2003.06.12, 2003.06.13, and 2003.06.14 Rational software products (this is not selectable). It will upgrade Rational XDE only if you have version 2003.06.00 or later. 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.

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

This service release enables you to manage v2003 IBM Rational XDE product's use of floating license keys.

To enable XDE license enforcement:

  1. Install the service release.
  2. Run the command <rational_directory>\common\SetXDEFloating.exe, where <rational_directory> is typically C:\Program Files\Rational. After running SetXDEFloating.exe, users will need a license key to use XDE.

After you configure XDE to use license keys:

  1. Get your license keys from AccountLink. Go to http://www.ibm.com/software/rational/support/licensing. Register with IBM Web Management and click Request and Manage License Keys. Passport Advantage customers can obtain XDE license keys by referring to the "Important Licensing and Installation Information" document in your shipment or the "Proof of Entitlement" certificate. 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.
  2. Install the IBM Rational License Server. If you do not have the license server software, you can either install it from the IBM Rational Solutions for Windows CD-ROM or download it from https://www6.software.ibm.com/reg/rational/rational-i. Refer to the IBM Rational Software License Management Guide on the IBM Rational Solutions for Windows Online Documentation CD-ROM for instructions on installing and operating the IBM Rational License Server.
  3. Launch the IBM Rational License Key Administrator and point the client machine at your IBM Rational License Server.

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

A valid XDE license key is required throughout the duration of any XDE session, which is initiated when a model is opened and terminated when all models are closed. When the session begins, an attempt is made to check out a license key from the license server. If a license is available, XDE checks out the key for the duration of your session. If no XDE license keys are available on the server, a warning message appears informing you that you do not have a valid key. XDE will continue to operate, and you will continue to see this message while using XDE until a valid license key is acquired.

Compatibility Issues

With Rational Products

Rational XDE with Rational PurifyPlus

Product Documentation

For information about accessing the online Help provided with Rational XDE, please see "Getting Started" in the Rational XDE Version 2003.06.15 Release Notes for new product installations. For download instructions, see the Scope section above.

Help Behavior

HTML with Active Content

When using this product on Microsoft Windows XP Professional, Service Pack 2, you may receive warnings when using online Help. The HTML-based Help files contain active content that is on the hard-disk of the local machine. Also see defect 463810 below.

Rational Developer Network Links

Because the Rational Developer Network is now IBM developerWorks Rational, the links to the Rational Developer Network from the Rational XDE Help system may not work properly. If you are not redirected to the correct page, please go to http://www.ibm.com/developerworks/rational/ and navigate or search from there.

Data Modeling

Information About Creating Databases (for XDE 2003.06.15 Service Release)

The procedure for creating a database has changed. The Open Specification menu item is no longer available on the Data Modeler menu; instead, use the Preferences dialog box to set the default database target and then create the database element.

The following information is an updated version of the "Creating Databases" topic for Data Modeling in Rational XDE:

Creating Databases

Before generating a DDL or database, you must specify a database target and assign the tables in the data model to a component stereotyped as «Database». It is recommended that you create only one database component for each data model.

To create a database:

  1. Set the default database target.
    1. Cick Window > Preferences.
    2. In the Preferences dialog box, expand Rational XDE, expand Data Modeler, and then click Database Defaults.
    3. On the Database Defaults page, select a target from the Default Database Target list and click OK.
  2. Do one of the following:
    • In the Data Modeler tab of the Toolbox, click the Database tool, and then in the diagram window, click where you want to place the database. A database component is displayed in the diagram window and in the Model Explorer as an element in the data model.
    • In the Model Explorer, right-click the data model, and then click Add Data Modeler > Database. A database component is displayed in the Model Explorer as an element in the data model.
  3. In the Model Explorer, double-click the database and type a unique name for the database that corresponds to the naming conventions of the database target.

Information About Enhancements to Compare and Sync Wizard (for XDE 2003.06.13 Service Release)

The following information is not included in the documentation for Data Modeling in Rational XDE:

Comparing and Pairing Data

The Compare and Sync Wizard has been enhanced to include a Choose Schema dialog box a new Compare dialog box in place of the Select Synchronization Options dialog box. The Compare dialog box lets you scroll through all the database items you want to compare and synchronize, it also includes expand and collapse buttons on the toolbar to help you review your data items in outline form.

Each data item, such as tables or columns, is shaded in a color to help you differentiate the beginning and the ending of all the properties and tagged values of that item.

Differences are identified by a red font accompanied by a red triangle. The toolbar includes the import, export, delete, and ignore buttons, so you can set actions for data items with a difference.

One of the new features added to the wizard is pairing. Pairing lets you align or map data elements that are the same element in the data model and the database or DDL, but are named differently. Pairing will save the tagged values of the data element. Pairing is controlled by a Pair button on the toolbar.

To pair data elements:

  1. Click a data item.
  2. Click the Pair button.
  3. Click the matching data item.

You can also separate paired data items by clicking the Unpair button.

After you assign actions to each data item with a difference and pair the data items you want to pair, you can click Next to continue in the wizard.

Modeling

Information About Editing Event Parameters in the Diagram Window (for XDE 2003.06.13 Service Release)

The following information is not included in the documentation for Modeling in Rational XDE (defect 247772).

Call Event Parameters Now Appear in the Diagram Window

Parameters of an unqualified event are surrounded by a double backslash (\\), similar to messages. When you edit parameters inline using the diagram window, the parameters are created or changed for the specific event. However, on a qualified event (one with an operation), operation parameters appear. When you edit the operation parameters, the changes are ignored and are not reflected in the diagram window, regardless of whether the event has additional parameters or not.

Round-Trip Engineering

Information About Exporting a .NET Code Model As a Reference Model (for XDE 2003.06.14 Service Release)

The following information is not included in the documentation for Round-Trip Engineering in Visual Studio .NET editions of Rational XDE (defect 249279).

Exporting a .NET Code Model As a Reference Model

When working with a Visual C# .NET or VB.NET code model, you can choose to export the model as a reference model. By using the Export as Reference Model command on the Round-Trip Engineering toolbar, in the context of the Model Explorer, you make a copy of the code model, modify its properties to transform it to a reference model, and then save it in the same folder as the assembly built from the project.

This export operation can be used to create a reference model when sharing components. For example, you might provide components to other people at the end of an iteration of development. As part of the documentation, you might provide the code model associated with the project that built the assembly. When another user references this assembly from a development project and synchronizes, a reference model associated with this assembly will created by the XDE Round-Trip Engineering (RTE) engine instead of using the supplied code model. This is intentional. In the Visual Studio .NET Edition of XDE, the code model and reference model are two different entities and one cannot be used in place of the other. Currently, there is no interopability between these two kinds of models. In order to help the process of "releasing" a code model along with the assembly built from that project, use this Export as Reference Model command.

If you want to include the code model of a project along with the assembly built from that project, you should export this code model as a reference model and then bundle that along with the assembly. This way, when another user references your assembly directly, the RTE engine will automatically detect the reference model colocated with the assembly. Note
that more than one reference model may be generated, depending on how many other code models, if any, your code model references directly or indirectly. You should include all the generated models along with the assembly.

When using this command, consider the following information:

This command will end with an error if any one of the following is true:

Information About Setting Initial File Structure When Generating C# and Visual Basic Code (for XDE 2003.06.13 Service Release)

The following information is not included in the documentation for Round-Trip Engineering in Visual Studio .NET editions of Rational XDE.

Initial File Settings for C# and Visual Basic

When you add C# and Visual Basic model elements to a nested namespace and then generate code, initial code source files are generated in the project's root directory by default. You can set code-generation options for C# and Visual Basic so that initial files are created in a folder structure that parallels the namespace nesting structure.

To define the location of initial files during code generation:

  1. Open the Options dialog box, expand Round-Trip Engineering, and then click Code Generation Settings.
  2. Select the Create directories for nested namespaces check box
  3. Click OK.

Web Publishing

Information About Publishing Multiple Models (for XDE 2003.06.15 Service Release)

The following information is not included in the documentation for Web Publishing in Rational XDE (defect 141376).

Publishing Multiple Models

You can create a list of models and then publish all of the models in the list at one time.

When you publish multiple models, you must specify the full path of the root file. This is the file that you open with a browser to display the top-level view of the models. If you open any of the other generated HTML files stored in the same folder as the root file, or in any of the model subfolders, only a portion of the model is available.

Because the model publishing tool generates many files along with the root file, the Publishing Multiple Models feature organizes these files with each published model in its own folder.

To publish multiple models:

  1. Open one of the models that you want to publish.
  2. Click Tools > Publish Multiple Models.
  3. Under Add Model to the list, click Browse and specify a model.
  4. Select a level of detail for publishing the model.
  5. Click the Add button to add the chosen model to the list.
  6. Repeat steps 3 to 5 to add more models.
  7. Optionally remove a listed model by selecting it and clicking the Remove button.
  8. Under Published model root, click Browse and specify a path for publishing the models.
  9. Click Publish to publish the listed models.
  10. Click Close to close the dialog box and save the list. When the dialog box is opened again, it will show the same list of models.

After publishing, the list of models is stored at the location that you specified for published models.

Restrictions and Guidelines on Using this Release

Data Modeling (for XDE 2003.06.14 Service Release)

Data modeling database connections need to be updated for Rational XDE version 2003.06.13 or later. For detailed information about the correct setup steps and connection parameters, see the following technotes on the IBM Support and downloads Web site:

Also see the Data Modeler defects listed under Known Issues.

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)

Defects and Changes

Known Issues

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

In Rational XDE 2003.06.15 Service Release

Category

ID

Description

Documentation
141376
Update online Help to include procedures for publishing multiple models. See above, under Product Documentation, Web Publishing.
1081391/APAR
IC45594

Update online Help to include corrected procedure for creating databases. See above, under Product Documentation, Data Modeling.

Installing and Uninstalling
376974/APAR IC40695
Installing Rational XDE on a system that has unsupported shells may result in installation error messages. During the installation process, it is possible to select an unsupported shell or have it selected by default. If you continue the installation to an unsupported shell using the installation wizard, you may see installation errors or a partial installation with no errors. XDE will not function properly in this scenario. You must select a supported shell before continuing with the installation.
Web Publishing and Reporting
463810
If you are running Rational XDE with Microsoft Windows XP Professional Service Pack 2, you may see an error message when attempting to view published models. The default security restriction in Service Pack 2 prevents users from opening local Web pages with active content. Instead, the following message is displayed in the browser: “To help protect your security, Internet Explorer has restricted this file from showing active content that could access your computer."

Workaround: You have two choices for dealing with this security restriction.

To display the content while maintaining your default Internet Explorer settings for Windows XP Professional Service Pack 2:

  1. Click the message bar and click Allow Blocked Content.
  2. In the Security Warning dialog box, click Yes to display the Web page content.

To display the content by modifying the Internet Explorer settings:

  1. Start Internet Explorer.
  2. Click Tools > Internet options.
  3. Click the Advanced tab.
  4. Under Security, select the Allow active content to run in files on My Computer check box.
  5. Apply the change, restart the browser, and access the content.

In Rational XDE 2003.06.14 Service Release

Category

ID

Description

Data Modeler
139953

When using .NET version of Rational XDE, unable to connect to IBM DB2 zSeries data model.

Workaround: Install DB2 Connect Personal Edition version 8.1 (or later) on your system.

140415

Users upgrading from Rational XDE 2003.06.12 to 2003.06.13 or later should be aware that the ODBC driver is no longer supported for connecting to a database.

Workaround: Instead, for most database systems, the JDBC Thin driver or ADO.NET should be used to connect. For more information, see Restrictions and Guidelines on Using this Release, Data Modeling.

140416, 140865

As of Rational XDE 2003.06.13, the details for connecting to IBM DB2 and Oracle databases have changed. In addition, the list of supported drivers has changed. In some cases, the following error message is displayed during a test connection: "Unable to connect to the database with the specified information. Please verify the connection information."

Workaround: For more information, see Restrictions and Guidelines on Using this Release, Data Modeling.

728904

Certain versions of the client connection tools (DB2 UDB Personal Edition or DB2 Connect Personal Edition 8.1) may stop working with the DB2 UDB database system. This may cause the reverse-engineering process to freeze when going from the database to the data model in XDE.

Workaround: First, generate the DDL script from the database, and then reverse engineer from the DDL script to the data model.

Documentation
249279
Update online Help to include details about the Export as Reference Model command, for exporting .NET code models to reference models. See above, under Product Documentation, Round-Trip Engineering.
Installing and Uninstalling
460902/APAR
IC42702

Installing Rational XDE - .NET Edition on a machine running Microsoft Windows XP, Service Pack 1, can result in slow performance for Visual Studio .NET., not only for Rational XDE projects but also C#, Visual Basic, and other projects.

Workaround: Upgrade to Windows XP SP1a. If Windows XP SP1 is required, then reducing the hardware acceleration on the Display Control Panel's Advanced Settings panel will alleviate the problem.

In Rational XDE 2003.06.13 Service Release

Category

ID

Description

Documentation
247772
Update online Help to address editing of event parameters in diagram window. See above, under Product Documentation, Modeling.
459662

The online Help for freezing a model incorrectly states an expected setting. In steps 3 and 4 of the "Freezing Include Models" topic, you are told to look for the text unitPolicy ="1". Instead, you will normally see unitPolicy="0" when opening a .mdx file.

Installing and Uninstalling
248305

When upgrading from Rational XDE Version 2003.06.12 to 2003.06.13, code template CLR callouts do not operate.

Workaround: Following an upgrade, CalloutCLRManager.dll must be reregistered manually using the regasm.exe utility.

To register using the command line:

  1. Change the directory to <install-location>\Rational\XDE\Addins\codetemplates\assemblies.
  2. Enter the following on one line, where drive is the drive where the MS .NET Framework is located and version-number is the Framework version number, such as 1.0.3705:
    <drive>:\Windows\Microsoft.NET\Framework\v<version-number>\RegAsm.exe CalloutCLRManager.dll
Round-Trip Engineering
138156

When working in a team development environment, unsynchronized items can result if one user accesses a solution using Rational XDE Version 2003.06.12, and a second user accesses the solution using version 2003.06.13 of XDE. The synchronization problem can happen if the version 2003.06.12 user fails to synchronize the solution before closing the solution, and the second user opens the solution from the 2003.06.13 version of XDE to work on the same model elements.

Workaround: Use one of the following workarounds:

  • Synchronize a solution before closing it and delivering changes to your configuration-management solution. This is a best practice and helps prevent many synchronization issues.
  • Before you begin to make additional modifications in a solution, run the Reset Synchronizer command to ensure that all prior changes in code and model are synchronized:
    1. After rebasing your project, open the shared solution.
    2. Right-click the solution or project node in the Solution Explorer, or right-click the model
      root in the Model Explorer, and then click Reset Synchronizer.
Web Publishing and Reporting

374617

When you publish a model, upon first opening the model you may see the following error message, "Page cannot be displayed."

Workaround: The Web publishing facility cannot access the contents of a model unless the Model Explorer in XDE can access them. For example, constraints that are not visible in the Model Explorer will not be published. The filter settings for the Model Explorer determine what is visible.

To modify filter settings for the Model Explorer:

  1. On the Window menu, click Preferences.
  2. Expand Rational XDE, click Model Explorer, and then click the Filter Settings button. The Model Explorer Filter Settings dialog box is displayed.
  3. In the Display the following elements list, select all the model elements you want to appear in the Model Explorer. Any elements you do not select will be hidden when publishing.
  4. Click OK.

In Rational XDE 2003.06.12 Service Release

Category

ID

Description

Configuration Management
243561

If you rename a model element or add a diagram to a saved and checked-in model, the dialog box that appears has buttons only for Checkout, Edit, and Help. The dialog box does not have a Cancel button.

If you click the Checkout button, and then click the Cancel button in the next dialog box, the in-memory changes are kept rather than being rolled back.

Workaround: If you want to add a diagram to a saved and checked-in model, you need to explicitly check out the storage unit of the diagram. The checkout must be done before making any changes to the model. If you did not check out the model, you can recover by closing the model without saving the changes.

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.

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.

245889/APAR IC39101

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,
461206/APAR
IC42781
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/APAR IC39101
See the description for defect 245889 above, in the "Data Modeler" section of this table.
Installing and Uninstalling
137334
If you are reverting from Rational XDE version 2003.06.12 to an earlier version of XDE, such as version 2003.06.00, you may see error messages during synchronization. See defect 137334 below for a complete description.
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 Options dialog box (on the Tools 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."

Round-Trip Engineering
135148
The Visual Studio .NET 2002 shell supports only 64 pages in the Options dialog box (click Tools > Options). Each of these pages is identified by a registry entry in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.0\ToolsOptionsPages

On a standard Visual Studio .NET installation with XDE installed, the number of Options pages exceeds the aforementioned limit. Therefore, the following two Rational XDE pages in the Options dialog box for Visual C++ settings may not be displayed:

  • Rational XDE\Round-Trip Engineering\Visual C++ Settings\Visual C++ Initial File Settings
  • Rational XDE\Round-Trip Engineering\Visual C++ Settings\Visual C++ Containers

As a result, it is not possible to configure the settings on the affected pages.

Workarounds:

  • Manually remove some of the registry entries for pages that are not used.
  • Upgrade to Visual Studio .NET 2003.
  • Microsoft may include a fix in a future service pack for Visual Studio .NET 2002. Check the MSDN download site for the availability of service packs for VS .NET 2002.
135490

If you create a project with Rational XDE models in Visual Studio .NET 2002, and then subsequently upgrade the IDE to Visual Studio .NET 2003, upon reopening the project, the Miscellaneous Files project in the Solution Explorer may appear to have duplicate versions of each referenced assembly model. This condition occurs after you reinstall XDE in Visual Studio .NET 2003, open up the project, and then synchronize the project or open the model.

The apparently duplicate models are actually separate versions. After the upgrade to the new IDE version, both Visual Studio 2002 and 2003 versions of each referenced assembly model are shown under the Miscellaneous Files project in the Solution Explorer. Although the references to assembly models point correctly to the Visual Studio .NET 2003 versions (vs7rte\vsnet\Models\v1.1\*.mdx), the display of the apparent duplicate assembly models may be confusing. However, this condition does not affect synchronization or cause actual problems of any kind.

Workaround:

To remove unused duplicate reference models from the project:

  1. Open your project in Visual Studio .NET 2003.
  2. In the Solution Explorer, select a reference model file in the Miscellaneous Files project.
  3. In the Properties window, view the File Path property.
  4. For those reference models that reside in the ..\vs7rte\vsnet\Models\v1.0 directory, right-click the model, and then click Remove.
  5. Repeat steps 2 through 4 for each duplicate reference model.
  6. Close the solution (save as needed) and exit Visual Studio .NET.
    When you open VS .NET the next time, you should not have this issue.

Note: This procedure removes the model files as project items from the Miscellaneous Files project, but it does not delete them from the file system. If you remove a correct model by mistake, the model will be recreated in the project at the next synchronization.

136904

Visual Studio .NET 2003 (devenv.exe) may hang indefinitely when using Visual C++ support in Rational XDE 2003.06.12. This can happen when running on:

  • Windows 2000 Professional SP2, SP3, or SP4
  • Windows 2000 Server SP2, SP3, or SP4

Workaround: If this problem occurs under this set of conditions, you must reboot the computer by turning it off and back on. This issue with the Windows 2000 kernel is Microsoft support case SRX031219604116. For the related Knowledge Base (KB) article and to learn about any hotfix, see article number 837443 at http://support.microsoft.com/?id=837443. IBM Rational customers can also contact Microsoft support directly for the hotfix, at the toll-free phone number(s) listed on http://support.microsoft.com, by simply referencing the KB article number (837443) for this problem.

137334

Error messages may appear during synchronization if you have reverted from the Rational XDE version 2003.06.12 Service Release to an earlier version of XDE.

Workaround: Use the following procedure as a guide when synchronizing.

  1. Create a C# Class Library project.
  2. To synchronize, click the Synchronize button on the toolbar.
    The Unknown RAS File Type dialog box opens.
  3. Type .mdx and click OK.
    The RTE.ModelMonitor.UpgradeProfile dialog box opens.
  4. Click OK.
    The synchronization completes.
  5. Delete the rte.prx profile located in the default directory. Typically, this is
    C:\Documents and Settings\user\Application Data\Rational\XDE\Profiles.

The next time you synchronize, the correct profile is applied.

137444

If you are using Rational XDE with Microsoft Visual Studio .NET 2003, you may see the following error message after using the Visual C++ Round-Trip Engineering feature in a solution containing a Managed C++ Windows Form project and adding a new form to the project:

"The designer could not be shown for this file because none of the classes within it can be designed."

The form fails to open up in the designer and the message appears in both the designer form and the task list. This error happens most frequently on Windows 2000 and is the result of an "out of memory" problem.

Workaround: To free up contiguous memory:

  1. Close the solution (first use Save All as appropriate).
  2. Close Visual Studio .NET.
  3. Start Visual Studio .NET
  4. Open the solution. The form opens correctly.
RXE
243418
The RXEMenuExtender target tag <AppendSelection> currently appends only the specific elements selected. It will not append a grouped set of elements.
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.
244558
All storage units in models under configuration management control in .NET must be explicitly checked out before running XDE Menu Extensions that attempt to modify them.
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.
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.

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
232204
Synchronization between ASP.NET and XDE Web Services is not supported under Windows NT 4. This is a known issue with Visual Studio.NET and there is no workaround.
239560, 241074
When you import or export large models using the XML Metadata Interchange (XMI) file format, the Rational XDE import and export process may hang/stall or a java.lang.OutOfMemoryError message may appear. To prevent the hang or error message, you must change the default Java Virtual Machine (JVM) size setting from 256 MB to a larger size.

Use the following steps to increase the JVM size setting within the Registry:

  1. Close Rational XDE and Microsoft Visual Studio .NET.
  2. Open the Run tool available from the Start menu.
  3. Type regedit in the Run window, and then click OK.
  4. Navigate to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\RationalSoftware\RJCB\JVMs\XdeJavascriptJvm.
  5. Locate the JvmOptions string value.
  6. Change the "-Xmx256m" JVMOptions string value to a bigger size, such as "-Xmx448m".

Note: The actual size of the JVM should be smaller than the physical RAM size of the computer, and must be multiple increments of 1K (or 1024 bytes).

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.

244167

If you upgrade your Microsoft Windows 2000 Terminal Server to Service Pack 4 (SP4) from SP3 and then try to use the Rational XDE version 2003.06.12 Service Release, you may experience a package load failure.

Then, on exiting Microsoft Visual Studio .NET, you may get an application error:

The instruction at "0x791bad3a" referenced memory at :0x00000050". The memory could not be "read".

This behavior happens when the following conditions are met:

  • You log on to the Terminal Server as a limited user (a user without administrator rights).
  • The Terminal Server is running Windows 2000 SP4 and has the .NET Framework 1.0 SP2 or earlier installed.
  • You have not installed the .NET Framework 1.1 or later on the Terminal Server.

Workaround: This is a known Microsoft issue. Please refer to http://support.microsoft.com/default.aspx?kbid=823485.
To work around this problem, install the Microsoft .NET Framework 1.1 on the Windows 2000 SP4-based Terminal Server.

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.

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.

Defects Fixed

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

In Rational XDE 2003.06.15 Service Release

Category

ID

Description

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

In Rational XDE 2003.06.14 Service Release

Category

ID

Description

General XDE
247693/APAR IC40927
Hotspots created for elements contained in swimlanes (whether merged or not) may not be placed in the expected location.

In Rational XDE 2003.06.13 Service Release

Category

ID

Description

Compare/Merge

513643

 

When working with XDE, two users may create storage units with the same name in their versions of the same directory. When the users attempt to check in or deliver their work and a merge is triggered, ClearCase will prompt the user to choose between the two storage units and XDE Compare/Merge will independently ask the user to choose between the two model elements associated with those storage units. In this situation, it is important that you choose consistently. That is, if you choose one user's storage unit, then you should also choose that user's model element associated with that storage unit. For example, suppose both users created class1 as a separate unit in a file named class1.clx in their versions of the same directory. The ClearCase directory merge will ask which of the two class1.clx files should be present in the merged directory and XDE Compare/Merge will ask which of the two class1 model elements to present in the merged model. If the user chooses the first user's class1.clx file during the ClearCase directory merge, then the user should also choose that user's class1 model element during the XDE Compare/Merge session.

Note that if the model element names differ but the storage units are the same, a similar situation arises but the behavior differs. For example, both users might initially create class1 in storage units class1.clx in their versions of the same directory. Then, the first user renames the class1 model element to be myclass. The storage unit retains the name class1.clx. However, in this case XDE Compare/Merge will allow both model elements class1 and myclass into the merge result model even though the ClearCase directory merge will permit only one class1.clx to reside in the directory. The resulting model will be unable to locate the missing storage unit. To recover from this, you should rename the missing class1.clx file to some other name and then locate this renamed file using the Browse to Unit command on the shortcut menu for the model element that is missing its unit. Perform the rename using the ClearCase Explorer or at a cleartool command line so that the history of the renamed file (which includes the file with its original name) is preserved.

Configuration Management
239946
Users who created cross-model references that resolve through XDE version 2002, Release 2.1 Service Release VOB-root registered locations must use a snapshot view the very first time these models are opened in XDE version 2003.06.xx, which will result in these models being upgraded. Once the models are upgraded and checked in, the models can be accessed in a ClearCase dynamic view.
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 button.
Data Modeling
241098

If you have no existing data model, the Class to Table Transformation dialog box does not open when you use the Class to Table command on the Transform menu.

Documentation
375451
The Help for Visual Trace should include the following text: "You must engage Visual Trace before starting the application to be traced."
Internationalization
240169, 240232,
594953, 595310, 596012, 596551
XDE cannot be installed into a path that includes Japanese or double-byte characters.
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.

Installing and Uninstalling
137827

When uninstalling 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.

447417
The following issue only applies to the Rational XDE Developer Plus Edition: To correctly configure a SitePrep area for XDE, Rational recommends that you do not use SitePrep.exe directly. Use Setup.exe and select Enterprise Install mode to create the SitePrep area. If you use SitePrep.exe directly, the SitePrep area may not be properly configured and an install performed from the improperly configured area may hang.
Round-Trip Engineering
138156

When working in a team development environment, unsynchronized items can result if one user accesses a solution using Rational XDE Version 2003.06.12, and a second user accesses the solution using version 2003.06.13 of XDE. The synchronization problem can happen if the version 2003.06.12 user fails to synchronize the solution before closing the solution, and the second user opens the solution from the 2003.06.13 version of XDE to work on the same model elements.

RXE
239228

For generalization, dependencies and realizations, the methods/properties to access the end elements return the opposite end. Specifically:

  • IRXEGeneralization.SuperElement returns SubElement
  • IRXEGeneralization.SubElement returns SuperElement
  • IRXEDependency.SupplierElement returns ClientElement
  • IRXEDependency.ClientElement returns SupplierElement
  • IRXERealization.SpecificationElement returns ImplementationElement
  • IRXERealization.ImplementationElement returns SpecificationElement
240004

The methods IRXEReference.Resolve() and IRXEReference.getRefModel() always return Null. A call to resolve() will resolve a reference, if possible, but it will still return Null.

Visual Trace
446505

Visual Trace does not support tracing ASP.NET applications on the Microsoft .NET Framework version 1.1.

Web Publishing and Reporting
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.

374690
If you publish a model that includes global actions, those actions are not represented in the published model.
General XDE
238301

The cross-model reference adornment is not displayed in the correct position in the print preview or when you paste the shape into other applications such as text editors.

238555

When you open a saved model that initiates specific internal processes to open a diagram, the model appears in the unsaved or modified state (with an asterisk next to the model name in the Model Explorer), even if you made no modifications to the model. You can safely save or discard the changes without data loss.

238740

When you work with subunits, it is recommended that you save your work by using the Save All command on the File menu. If you use the Save command (or Ctrl+S), your work may not be saved consistently.

For example, you may change one subunit, which results in changes in two other subunits. If you save only the first subunit and not the two others, the files saved on disk will be inconsistent with one another. If, instead, you use the File > Save All command, all three changed files will be saved to disk and the files on disk will be consistent with one another.

241211

You are prompted to check out the file if you open a diagram within a source-controlled model and page breaks must be updated due to prior changes in the diagram elements. However, clicking Cancel does not dismiss the dialog box. (This happens if the Prompt for check out setting is selected on the Source Control, General page of the Options dialog box.)

241325
During the model upgrade process (especially with non-US English models), the XDE print preferences may not upgrade correctly.
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.

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.

246125
Users of Rational XDE Developer Plus for .NET Platform Edition may see the following license error message when launching Rational PurifyPlus, PureCoverage, or Quantify products: "Failed to check out a key for PurifyNT: FLEXlm Error - 18, License server does not support this feature." This may occur when additional Rational products are installed alongside XDE.
246155
If you have license enforcement activated for Rational XDE (Developer Plus for .NET Platform Edition), using a Rational Suite license key for PurifyPlus causes Visual Studio .NET to crash on exit. If the condition is of concern, please contact your IBM sales representative, who can investigate making available an alternate license key.
589765 (55216)
If you use the High Contrast display option for Windows 2000 Accessibility, the cursor is not visible in Rational XDE diagrams.

In Rational XDE 2003.06.12 Service Release

Category

ID

Description

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.

Round-Trip Engineering
136715

Rational XDE reverse engineers Microsoft Visual Studio .NET Web projects into a new model file with no contents from the source project.

This issue was fixed by changing the Rational XDE HTML parser to be case-insensitive when looking for HTML tags. If the parser is unable to parse a file, it reports the error and continues with the next file instead of aborting the synchronization. Writing of aspx, asmx, and ascx files is now more robust on both VS.NET 7.0 and 7.1.

137288

A reverse-engineered class is added to code within a code template expansion, leading to unexpected behavior. If a class has a code template bound to it, then a nested class, field, or operation added to that class in the model may get generated within the code template expansion in code during synchronization. This added item is deleted during code template expansion upon the next synchronization.

137427
Having a code template bound to a class prevents a user from deleting elements in the class from the Model Explorer. The auxilliary synchronization performed on model elements with a code templates bound to them, or on model elements whose stereotype has been changed by the user, causes any deletions made by the user within that element in the model to be ignored upon synchronization.
244203/APAR IC37806

XDE code templates bound to classes causes data loss. The binding of a code template to a class while at the same time modifying a model element in the class (for example, adding a parameter to an operation) causes the class to be deleted upon synchronization.

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

If you are using Microsoft Visual Studio .NET 2003 and are a member of the the Debugger Users group in Windows, the list of classes you select for monitoring by Visual Trace wil not be retained once you close the Class Selection Wizard.

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.
Visual Trace
241395, 514239
If you are using the Rational PurifyPlus or Visual Trace features to observe a program running under Microsoft .NET Framework 1.1, the observed program may crash with an "uncaught exception" message. If the error message refers to a library called BCIEngCOR.dll and includes the error code number 0x80000003 or the words "user breakpoint," then this error is caused by a known .NET Framework defect.

Contacting IBM Rational Software Support

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

Voice Support is available to all current contract holders by dialing a telephone number in your country (where available). For specific country phone numbers, go to www.ibm.com/planetwide.