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

Release Notes

Version 2003.06.16, November 2006

(For new product installations)

Last Updated: 11/06/2006
GI11-4683-06


Copyright © IBM Corporation 2002, 2006. 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 new product installations of the Microsoft .NET editions of IBM Rational® XDE™ Version 2003.06.16. Some information is specific to a product package, and is designated accordingly.

Go to the release notes for Rational XDE version 2003.06.16 Service Release if you are upgrading from:

The release notes document for the Service Release highlights added capabilities, changed software requirements, installation information, new compatibility issues, further restrictions and guidelines, and known and fixed defects since the above releases.

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

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.

Choosing the Product to Install

Although packaged and purchased together, IBM Rational Rose and IBM Rational XDE are installed separately. You can use them in combination, with some limitations; however, most users will benefit from primarily using one tool or the other. In general, Rational XDE provides more advanced modeling capabilities than Rational Rose, and should be your primary choice. However, in some situations you may choose to use Rational Rose, and migrate to Rational XDE at some later time. In other situations, some team members may choose to stay on Rose indefinitely (for example, to support Microsoft Visual Studio 6) but must work with others using Rational XDE (for example, to support Visual Studio .NET).

To understand which tool to install, review the following table:

Product Your Goal... Install
All IBM Rational Rose XDE family members
  Require IBM Rational or third-party add-ins only supported by Rational Rose Rose*
  Must work tightly with a team using IBM Rational Rose Rose
  Must perform your modeling tasks on UNIX or Linux
Rose UNIX
  Require Ada language support Rose UNIX
  Are on a team or project already using Rose Rose**
  Are on a team or project already using XDE XDE**
  Have extensive SoDA reports based on Rose that have not been ported to XDE
Rose
  Have developed custom tooling which uses the Rose API Rose
  Require collaboration diagrams Rose
IBM Rational Rose XDE Modeler
  Requires business modeling stereotypes compatible with the Rational Unified Process business modeling discipline Rose†
IBM Rational Rose XDE Developer for Java
  Use Eclipse as your Integrated Development Environment (IDE) XDE
  Use IBM WebSphere Studio as your IDE
XDE
  Are using Borland Jbuilder, Visual Age, or other IDE Rose
IBM Rational Rose XDE Developer for Visual Studio
  Want to design and develop Visual Studio .NET applications
XDE
  Want to perform data modeling tasks such as schema design, database reverse
engineering, generate O/R mapping
XDE
  Want to design and develop Visual Studio 6 applications
Rose
  Want to develop ANSI C++ applications
Rose‡
IBM Rational Rose XDE Developer Plus
  IBM Rational Rose XDE Developer Plus combines Rose XDE Developer for Java and Visual Studio, and
adds support for ANSI C++ development in Eclipse, visual tracing of application execution, and IBM
Rational PurifyPlus.

* Contact your add-in provider to inquire about XDE availability.
** You may want to decompose your project to allow Rose and XDE to be used within the same project (for example, a
mixture of Visual Studio 6 and Visual Studio .NET development). Interoperability is outside of the scope of this document; please contact IBM Rational software support for further information.
† A RUP-compatible business modeling profile for XDE is available for separate download; please contact IBM Rational software support.
‡ ANSI C++ is also available to XDE users who purchase IBM Rational Rose XDE Developer Plus.

Contents

What's New in this Release
  New in All .NET Platform Editions of Rational XDE
  New in All .NET Platform Developer Editions of Rational XDE
  New in Rational XDE Developer Plus for .NET
Hardware/Software Information
  Client Requirements
Installing and Upgrading
  Identifying the Product Build ID
  Installation Issues
  Upgrading from Previous Versions of Rational XDE
  Installation Information
License Enforcement
Getting Started
  Starting Rational XDE
  Accessing Help
  IBM developerWorks Rational
Compatibility Issues
  With Rational Products
Product Documentation
  Help Behavior
  Data Modeling
  Modeling
  Round-Trip Engineering
  Web Publishing
Restrictions and Guidelines on Using this Release
  File Management and Configuration Management
  Rational XDE Extensibility (RXE)
  RequisitePro-XDE Integration
  Round-Trip Engineering
  Visual Trace
  Web Publishing and Reporting
Defects and Changes
  Known Issues in this Release
  Defects Fixed in this Release
Contacting IBM Rational Software Support

What's New in this Release

The items listed in this section provide an overview of the most important new features in this release. Refer to the online Help for details about these features.

The capabilities available to you in Rational XDE version 2003.06.16 depend on your packaging option. To determine the package you have installed, see Identifying the Product Build ID below.

For more information, see "IBM Rational Modeling Packages" in the Rational XDE Help.

New in All .NET Platform Editions of Rational XDE

Operating Systems

Asset Browser

The Asset Browser lets you add Internet-style indexing and browsing for all of your RAS assets—patterns, code templates, models—any asset you create with the Rational XDE RAS Packager.

Rational XDE Extensibility (RXE) API

New Rational XDE Modeling Project

Rational Suite Product Integrations

Enhancements to Patterns and Code Templates

XMI Model Interchange

Enhancements to Visual Studio .NET Integration

Enhancements to UML Diagramming and Printing

Enhancements to Web Publishing

Enhancements for Team Development

New in All .NET Platform Developer Editions of Rational XDE

New Round-Trip Engineering Features

Enhancements to Patterns and Code Templates

New Assisted Modeling Dialog Boxes for .NET Code Constructs

Data Modeling

New in Rational XDE Developer Plus for .NET

Visual Trace

Visual Trace automatically creates an enhanced UML sequence diagram from a running Visual Studio .NET C# or Visual Basic application.

Rational PurifyPlus

Hardware/Software Information

Client Requirements

Hardware Requirements

The following table provides minimum and recommended system configuration requirements for Rational XDE. Rational XDE runs under the minimum configuration; however enterprise-level development is enhanced when resources conform to or exceed the recommended configuration.

Keep in mind that performance has been tuned for the recommended system configuration. In general, increasing available memory (by adding more memory or closing other applications) increases performance, especially when working with large models. Performance during code-model synchronization is significantly impaired when performed on a system with a hard disk drive formatted using the FAT32 file system. NTFS is highly recommended.

Also note that the disk space required by your Rational XDE workspaces varies significantly, depending on the size and number of files you create. Rational XDE model files for analysis may be quite small, whereas model files for enterprise-level development may grow to be quite large, particularly when generated code is included in the calculation.

For more information about hardware configuration and performance, see "Rational XDE Performance" in Rational XDE Help.

Processor Pentium III-class processor at 500MHz; Pentium III-class processor at 1 GHz or higher recommended
Available RAM

Minimum: 512 MB. Recommended: 1 GB for Rational XDE Developer versions

Available Disk Space

Minimum: 500MB for installation drive, 100 MB for workspace. Recommended: 2-5 GB for workspace

Video Minimum screen resolution: 800 x 600 pixels, 256 colors. Recommended: 1024 x 768 pixels, 16-bit color or higher
Mouse/Pointing Device Any pointing device with at least two buttons

Software Requirements

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.
Operating System Languages

Level 1 support for these languages:

  • Dutch
  • Hebrew
  • Traditional Chinese
  • Korean

Level 2 support for these languages:

  • Japanese
  • German
  • Simplified Chinese
  • French
  • Italian
  • Swedish

Notes:

  • XDE cannot be installed into a path that includes Japanese, double-byte, or extended characters.
  • The ClearCase 5.0 XDE ClearCase Type Manager installer will not function if VOB directories contain 16-bit characters. Please see Internationalization in "Known Issues."
Supported Platforms
  • Microsoft Visual Studio .NET 2002
  • Microsoft Visual Studio .NET 2003

Note:

  • Windows NT is not a supported operating system for Visual Studio .NET 2003.
Internet Browser
  • Internet Explorer 5.5 with Service Packs 1 or 2
  • Internet Explorer 6 without any service pack or with SP1
  • Netscape 7.0
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.
Online Documentation Display and Printing Rational XDE documentation includes a document in Adobe® Acrobat® PDF format, requiring Adobe Acrobat Reader. You can download the Acrobat Reader with Search installation kit from the Adobe Web site, at http://www.adobe.com/products/acrobat/alternate.html.
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
Rational RequisitePro To use the RequisitePro-XDE Integration, you must have RequisitePro version 2003.06.16 installed on your system.

Configuration Management Software

Supports:

  • Rational ClearCase version 2003.06.00 or later and ClearCase LT version 2003.06.00 or later.
  • Rational ClearCase version 2002.05.00, with the latest required patch level installed.
  • Visual SourceSafe version 6.0c (with Visual Studio .NET 2002)
  • Visual SourceSafe version 6.0d (with Visual Studio .NET 2003)

XDE will display a warning message when the first model is opened if the ClearCase patch level on your system is less than as follows:

  • For ClearCase v.2002.05.00, patch 15

To verify the latest patch information for your version of ClearCase, go to
http://www.ibm.com/software/rational/support/upgrades/patches.html

To find out which patches your ClearCase installation has installed, use the cleartool -version command in a DOS command prompt window. 

Notes:

  • For enhanced model integrity, Rational recommends that you either install the most recent patches for ClearCase 2003.06.00 or later or disable enhanced ClearCase menus in Visual Studio .NET. For more information, see defect 240709, under "Known Issues."
  • Users installing recent ClearCase v2002.05.00 Windows patches (for example, patch 24 or 26) should see defect 245044 below.

Installing and Upgrading

Identifying the 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.

Installation Issues

General

Operating Systems and Languages

Rational ClearCase Integration

Rational RequisitePro

Upgrading from Previous Versions of Rational XDE

Installation Information

You can find the latest version of these documents in the IBM Publications Center at www.ibm.com/shop/publications/order by searching on their titles.

Also, be sure to review the installation issues listed in this document.

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.

Getting Started

Starting Rational XDE

Because Rational XDE is fully integrated into the Visual Studio .NET environment, there is no separate application to open; you simply start modeling your code within Visual Studio .NET. The easiest way to begin modeling when you have an existing Visual Studio .NET solution is to select the solution in the Solution Explorer and right-click Synchronize. If you do not have an existing solution, create a solution with one or more projects and create a model.

UML models are files stored as project items that you manage just as you manage any project item in Visual Studio .NET. For more information about beginning to use XDE, see the "Getting Started with Rational XDE" topics and "Modeling Applications and Generating Code with Rational XDE" topics in Rational XDE Help.

Accessing Help

For more information, see the "Help on Help" topic in Rational XDE Help.

IBM developerWorks Rational

IBM developerWorks Rational (www.ibm.com/developerworks/rational) is an online community that provides information and an exchange of ideas and best practices. Content on the site has been edited for quality and relevance, and organized by technology and process. In addition to these resources, you will find links to Web-based training. Use the site to:

Compatibility Issues

With Rational Products

Rational XDE with Rational ClearCase

Rational XDE with Rational PurifyPlus

Rational XDE with Rational RequisitePro

Product Documentation

For information about accessing the online Help provided with Rational XDE, please see Accessing Help 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

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

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

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 Setting Initial File Structure When Generating C# and Visual Basic Code

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

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

File Management and Configuration Management

Managing Rational XDE Model and Model Storage Unit Files

Certain file operations that are accessible in the Visual Studio .NET Solution Explorer and the Windows Explorer are not valid for Rational XDE model and model storage unit files. Please follow these guidelines:

Committing Your Changes to Rational XDE Model and Model Storage Unit Files

Rational XDE lets users subdivide models into sets of model storage unit files. Saving changes to an XDE model file does not automatically save changes to all modified storage units. Be sure to always save your model and storage unit changes at the same time.

Visual Studio .NET C++ Projects

Do not add Rational XDE model files to Visual C++ .NET projects. There are incompatibilities between XDE storage unit handling and C++ .NET project item handling.

Team Development with Microsoft Visual SourceSafe

Checking In Modified Files (Pending Checkins)

Rational XDE lets users subdivide models into sets of model storage unit files. Checking in an XDE model file does not automatically check in all of the model's storage units. Be sure to always check in your model and storage units at the same time.

Model Merging

If you configure a Microsoft Visual SourceSafe database to allow multiple checkouts, Rational recommends that all of the Rational XDE model file extensions be registered as binary file types with Visual SourceSafe prior to any files being added to a Visual SourceSafe database.

To do this, use either the Visual SourceSafe Administrator or Visual SourceSafe Explorer. Use the following procedure:

  1. From the Tools menu, click Options.
  2. Click the File Types tab.
  3. In the Binary files text box, append the following to the list of binary file types:
    , *.mdx, *.agx, *.acx, *.clx, *.cbx, *.cix, *.cmx, *.cnx, *.dgx, *.enx, *.inx, *.iix, *.ifx, *.ndx, *.nix, *.obx, *.pkx, *.sgx, *.smx, *.ssx, *.ucx

If there are pre-existing Rational XDE files in the database prior to performing this configuration, it is necessary to locate all the pre-existing artifacts in the SourceSafe Explorer and change their type to Binary manually using the properties of the file after the extensions are registered.

The effect of this registration process is that textual merge will never be performed on the XDE files. This is the desired result as only the XDE Compare/Merge facility will produce correct compare or merge results for XDE models. Files that are registered as binary will not permit multiple checkouts even if the SourceSafe database permits this for nonbinary file types.

Note: It is important that Visual SourceSafe administrators check this setting using the Administrator applet, but end-users should also check this setting using the Explorer.

Rational XDE Extensibility (RXE)

RequisitePro-XDE Integration

Recommendation for Teams Using the RequisitePro-XDE Integration

Some teams that use the RequisitePro-XDE integration can improve their multiuser compatibility by establishing a PathMap for both RequisitePro projects and XDE models. If your team uses the RequisitePro-XDE integration, and if your team also meets any of the following criteria, consider following this guideline:

If your team is a candidate for establishing a PathMap for RequisitePro projects and XDE models, see the information about establishing a PathMap in the Integration Help.

Note: Rational ClearCase UCM users should be aware that, typically, you do not need to invoke the RequisitePro-XDE integration from your Integration view, only from your Development view. However, if you must invoke the integration from your Integration view, then you will need to manually update your PathMap to accurately reflect the location of the model you want to work with in your Integration view. Additionally, note that the Help is inaccurate when it states that the PathMap topic applies only to Rational Rose. In fact, PathMaps are also used for the RequisitePro-XDE integration.

Round-Trip Engineering

Adding, Moving, and Deleting Classifiers in Subunits Can Cause Model Root Contention

Rational XDE stores all or part of a model in one or more files. When a model has been divided into separate files, the files—other than the main .mdx file—are called subunits (or storage units). If code file artifacts are not organized in a parallel structure with their associated model packages set as subunits, the model root will need to be checked out whenever classes are added or deleted inside their owned namespaces. (Defect 51443)

For example, consider two developers who own namespaces N1 and N2, respectively, where each namespace has been made a controlled subunit. If the first developer deletes the class Class1 from namespace N1, he or she would need to check out the model root, subsequently requiring a delivery and merge of model root changes. This condition results because Class1 is the supplier of an Element Residence relationship from the component Class1.cs, which is itself inside packages owned by the model root.

Workaround

Model root contention can be avoided by creating file folders for code subsets and making the corresponding directory packages subunits, thereby requiring that only the directory packages involved in the add, move, or delete operation be checked out.

You can do either of the following, each of which is described in a procedure:

To set up a team development structure on the code side:

  1. Create a new .NET project.
  2. Add folders that will parallel components owned by individual developers in the team development effort.
    1. In the Solution Explorer, right-click the project and then click Add > New Folder.
    2. Provide the new folder with a name that parallels the name of the component, namespace, or developer.
      For example, in a project with two developers working in separate namespaces, the folders N1Developer and N2Developer could be added.
  3. Add the class files to each folder that the developer owning the folder will work on: Right-click the folder and then click Add > Add New Item > Class.
  4. In each new class file, verify that the code namespace is correct.
    For example, in a Class1.cs file added to the N1Developer folder, change namespace Project1.N1Developer to Project1.N1.
  5. Synchronize the project to create or update the code model.
  6. Make the developer owned packages into subunits.
    1. In the Model Explorer, expand the Artifacts package and the project directory package, and then locate the new directory packages, N1Developer and N2Developer.
    2. Right-click the directory package and then click Make a Separate Unit.
    3. Right-click the corresponding namespace, N1, and then click Make a Separate Unit.
  7. Subsequently, new classes are simply added to the developer owned folders created above in step 2.

To set up a team development structure on the model side:

  1. Create a new .NET project and then synchronize the project to get a new code model.
  2. Add developer-owned namespaces by clicking the code model or root namespace and then clicking Add Language > Namespace. For example, you could add namespaces N1 and N2 for two developers.
  3. Add language-specific classes to the namespaces.
    1. Right-click the namespace and then click Add Language > Class.
    2. In the Add Language Class dialog box, enter a name for the class.
    3. In the Source File box, add the directory package location to the file name. For example, for a class Class1 being added to namespace N1, which is in turn owned by package N1Developer, type N1Developer\Class1.cs.
  4. Synchronize the project. New classes will be generated in files created in new folders.
  5. Make the corresponding packages into subunits in the model.
    1. In the Model Explorer, expand the Artifacts package and the project directory package, and then locate the new directory packages, N1Developer and N2Developer.
    2. Right-click the directory package and then click Make a Separate Unit.
    3. Right-click the corresponding namespace, N1, and then click Make a Separate Unit.
  6. Subsequently, new classes are simply added in these new folders as above in step 3.

Visual Trace

Socket Connection

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." (Defect 514577)

Consider the following options:

Web Publishing and Reporting

Documentation

For documentation about the Web publishing and reporting feature of Rational XDE, see the Reporting and Publishing_vsnet.pdf Adobe Acrobat file located at <install-drive>\Program Files\Rational\XDE\Addins\webpub. This information is not included in Rational XDE online Help.

Context-sensitive help (F1 or the Help button) is not available for Web publishing and reporting dialog boxes.

Java Plug-in

The Web publishing capabilities in Rational XDE require the Java Plug-in, available from the Sun Web site. This plug-in must be installed on any machine on which you want to view published models. If you have not already downloaded and installed the plug-in, you are prompted to do so the first time you use Web publishing in Rational XDE.

Note: If your machine is not connected to the Internet, you will not be notified about the need for the plug-in, and you will get errors when publishing.

To download and install the plug-in:

If you download and install the Java Plug-in version 1.4, you may need to change the default security settings to allow read permission. Follow these steps to change the default security:

  1. Locate the .java.policy file in your home directory. Create the file, if it does not exist.
  2. Append the following section to the end of the file:
    grant codeBase "file:/-" 
    {
        permission java.io.FilePermission "«ALL FILES»", "read";        
    };
  3. Save the file.
  4. Restart the browser.

Free Disk Space

Publishing models requires significant free disk space; use the following guidelines when publishing:

Defects and Changes

Known Issues in this Release

The following tables describe the known issues in this release, including issues found in Rational XDE Version 2003.06.16, Version 2003.06.15, version 2003.06.14, version 2003.06.13, version 2003.06.12, version 2003.06.01, and version 2003.06.00.

In Rational XDE 2003.06.16

Category

ID

Description

General XDE

475856

The Microsoft Windows operating system limits path names to 256 characters. This can result in an error message when you create file locations.

Workaround: Ensure that your path name includes fewer than 256 characters.

In Rational XDE 2003.06.15

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

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

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.

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

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

In Rational XDE 2003.06.01

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.

In Rational XDE 2003.06.00

Category

ID

Description

Compare/Merge
239157

Occasionally, you may see that the number of conflicts reported during an XDE Compare/Merge session appears to be inconsistent with the state of the conflict navigation buttons and menu items. For example, the status bar indicator may show that there are two unresolved differences remaining to be resolved when the Navigate to Next Unresolved Difference button and menu item are unavailable. This may happen when conflict resolution propagation automatically resolves other conflicts in response to a conflict you have resolved, as when you resolve a conflict involving the deletion and renaming of a class by deleting the class. In that case, the conflict resolution is automatically propagated to remove views of the deleted class from diagrams, thereby resolving dependent conflicts. However, the conflicts that are resolved automatically may not correctly be reflected by the conflict count.

If you encounter a situation where the status bar count indicates that there are differences remaining to be resolved, yet navigation to the next and previous unresolved differences is not available (dimmed), then the conflict count is incorrect; you have, in fact, resolved all conflicts. In this case, you can ignore any warnings about unresolved conflicts when you save and end your merge session or commit the merge session to ClearCase.

241028
If you encounter a reload dialog box after clicking Save and Commit ClearCase Session during an XDE Compare/Merge session, click No in the reload dialog box to avoid a possible shell freeze.
511988, 513261
When fusing three or more models, you may encounter cases where conflicting differences do not generate conflicts when there should be conflicts.

Workaround: Perform several sequential merge sessions in which you fuse two models at time in each session, until you have fused all of the models.

513914

When Rational ClearCase initiates an XDE merge session involving a diagram that is a separate unit, occasionally the diagram cannot be opened from the Model Explorer. This occurs when certain information necessary to open the diagram resides in a parent unit of the diagram unit and is, therefore, not present during the merge session.

Workaround: Once the merge session completes, you should be able to open the model and then open the diagram without difficulty.

Configuration Management
26272

If you change configuration-management options while using Rational XDE or Microsoft Visual Studio .NET, unexpected behavior may result and the new option settings may not be recognized. Microsoft is aware of this defect in Visual Studio .NET version 2002.

The following steps will reproduce the defect:

  1. Open a Visual Studio .NET project that is under source control.
  2. On the Tools menu, click Options.
  3. In the Options dialog box, click Source Control > General.
  4. Select Do nothing when checked-in items are edited and select Allow checked-in items to be edited.
  5. Modify a checked-in item in the project.
  6. Undo the modification.
  7. Return to the Options dialog box and select Prompt for check out when checked-in items are edited.
  8. Modify a checked-in item in the project.
    At this point, you would expect to see a message about checking out the modified item; however, the message will not be displayed.

Workaround: Restart the Visual Studio .NET session after modifying source-control preferences for the second time in a session.

238559

If you are using Microsoft Visual Source Safe as your configuration management software and share checked-out model files with other users, XDE may produce an error when you try to perform specific operations such as delete.

Workaround: Make the checked-out model files read-only and restart XDE.

239662

When upgrading older models, the profile upgrade process will not complete successfully if there are any missing model subunit files.

Workaround: A utility that fixes models in this state is available on the Rational Developer Network. If you cannot locate the utility, the Rational XDE v2003 Model Repair Tool, contact Rational Software Support for assistance.

240362

If you are using a ClearCase dynamic view and check in a model or subunit, triggering a composite object support dialog box that attempts to add a newly separated unit to source control, the operation fails in the second dialog box.

Workaround: Add the new subunits through pending check-ins, the Solution Explorer, or the Model Explorer. You must use ClearCase Explorer to check in parent directories that the second dialog box leaves checked out. This behavior is specific to dynamic views; the triggered subunit add to source control operations work as expected using snapshot views.

240709

For enhanced model integrity, Rational recommends that you either install the most recent patches for ClearCase 2003.06.00 or later or disable enhanced ClearCase menus in Visual Studio .NET. To disable enhanced ClearCase menus, clear the Override source code control menu items check box on the Rational ClearCase, General page of the Options dialog box.

510701

When performing an update with multiple conflicting control units, XDE may not merge all control units. In Rational XDE Developer - .NET Edition, the composite object versioning (COV) functionality is triggered by a change in the source control status of one of the model subunits. The post-processing that is performed may not trigger all the correct merge operations. This defect applies if you are using Rational ClearCase in single-stream mode in conjunction with XDE.

For example, two (or more) users are working within XDE and using ClearCase in single-stream mode:

  1. User1 creates a new solution.
  2. User1 adds the solution to source control.
  3. User1 creates a Rational XDE base model.
  4. User1 adds the following to the model:
    Package1
        Class1
    Package2
        Class1
        Diagram1
  5. User1 drags both classes onto Diagram1.
  6. User1 makes the units separated.
  7. User1 selects the root node and saves.
  8. User1 checks in the root node and sees the following message: "In order to ensure model Integrity in the source control system, the following files have been checked in for you. <List of files>"
  9. User1 clicks OK.
  10. User1 checks in his solution.
  11. User2 updates her view from outside the tool.
  12. User2 opens the solution.
  13. User1 renames Package1 and Package2.
  14. User1 checks in his changes.
  15. User2 renames Package1 and Package2 to names that differ from the names used by User1 (to create two conflicts).
  16. User2 checks in her changes.
  17. When asked which version to take, User2 keeps the current version in view.

The first merge does happen but the second (or any subsequent) merge will fail.

Workaround: The user should perform the checkin and merge on individual subunits.

510974
If you attempt to use applications or tools external to Visual Studio .NET to perform configuration management operations, problems may result. For example, if a package is checked out from outside of Rational XDE, and then checked in using XDE, the check-in fails.

Workaround: In this case, the check-in operation will succeed if tried a second time. However, Rational recommends that configuration-management operations always be executed from within the shell.

512493

After doing a checkin, you may be prompted for another activity, with three other files still checked out in the Pending Checkins dialog box: Project1.vssscc, Project1.vspscc, and Model1.mdx.rcsiproj.cm. These three files are internal to Visual Studio .NET. This is an informational message only and no user action is necessary or required.

512637

When using the Get Latest Version command to request the latest version of a model, the subunits may not be reloaded. You may see this if your project contains a Rational XDE model with subunits under source control, and some of the subunits are known to have been updated in another view, but the model file has not changed. The following steps reproduce the problem:

  1. Open the Visual Studio.NET project that is checked into source control.
  2. Open the model.
  3. Select the model root file (.mdx), right-click, and click Get Latest Version.
    No reloading is done.

Workaround: This behavior is due to a limitation in composite object versioning (COV). Because the model file does not change as a result of the operation, the COV capability is not triggered and no other model elements are updated. If an update is required, you should select an element that actually gets updated.

512638

Under certain conditions, the composite object versioning (COV) implementation fails to update the model and its associated subunits. This problem can appear if an XDE subunit is checked in and, during checkin, a merge is performed resulting in a more recent version of the subunit being made available. In such a case, it would be expected that the model and associated subunits are updated to reflect the more recent version of the checked-in subunit, which may contain changes affecting the model integrity.

Preconditions for this defect are as follows:

  • A ClearCase VOB is available.
  • Each user has their own snapshot view on that VOB.
  • Visual Studio .NET is configured to use Rational ClearCase.

The following is a scenario in which this problem may appear:

  1. User1 creates a new project, P1, and its associated solution.
  2. User1 adds the solution to source control.
  3. User1 creates a new model, M1.
  4. User1 creates a package, P1, and makes it a separate unit.
  5. User1 checks in the model.
    The model is checked in, along with all other subunits.
  6. User2 updates his view to get the latest version of the model.
  7. User2 starts Visual Studio .NET and opens the solution.
  8. User2 opens the model.
  9. User2 checks out P1.
  10. User2 adds package P2 under package P1 and makes it a separate unit.
  11. User2 checks in the model.
    The model is checked in, along with all other subunits.
  12. User1 checks out P1.
    A dialog box is displayed indicating that a more recent version of the file is available. The user is asked to select whether to check out the current version in view, or the new version.
  13. User1 opts to check out the current version of the package.
  14. User1 adds a class, C1, to package P1.
  15. User1 checks in P1, selecting to keep the subunit checked out.

Instead of this result, the preferred outcome would be for User1's version of package P1 to be merged with the version created by User2 so that both class C1 and package P2 are now part of the package. The model and its associated folder would be updated to bring in package P2's file. The model would be reloaded and both package P2 and class C1 would be visible in User1's workspace. All of model M1's subunits would then be checked in except for P1.

512740

When you add a new Rational XDE model to a project that is under source control, you are prompted to check out the associated solution file.

Workaround: Choose to check out the solution file and proceed.

513319

A Rational XDE model’s subunit files will not be updated if you use the Visual Studio .NET Open from Source Control command (on the File > Source Control menu) on a project that is stored in a Visual SourceSafe repository and that already exists in the working directory.

This defect applies to Rational XDE users who place their models under Microsoft Visual SourceSafe source control. It occurs under the following conditions:

  • A solution and project already exist under Visual SourceSafe source control.
  • The solution and project have already been opened from source control and their files can be found in the working directory.
  • The project contains a Rational XDE model with subunits.
  • A more recent version of the Rational XDE model exists in the repository.

If you then open the Visual Studio. NET project by clicking File > Source Control > Open from Source Control, then the Rational XDE model is updated, but not its subunits.

Workaround: Manually update the working directory using Visual SourceSafe commands before opening the project. This will ensure that all Rational XDE model subunits are also refreshed in the working directory.

513367

Users who place their models under Rational ClearCase source control and select the Keep items checked out when checking in check box on the Source Control, General page of the Options dialog box may see the following problem: Tthe composite object versioning (COV) functionality provided within Rational XDE will not execute the first time when checking in a newly created subunit that was previously checked in as a result of COV execution.

Workaround: Refresh the configuration management status of newly created subunits that are involved in a COV operation. This problem is due to how Visual Studio .NET handles files under source control.

514765

Subunits should not be added to models that are solution items (that is, models owned directly by a solution rather than a project). If you do add subunits to models that are solution items, when you reopen the solution, the following error message will be displayed for each separate subunit that XDE attempts to open: "The selected file is a Rational XDE unit file and cannot be opened separately in Rational XDE. Please open the corresponding model file (.mdx) instead." These warnings can be ignored, but it is much better to avoid subunits altogether in this situation.

Data Modeling
240103

When you use JDBC for DB2 connections, you must verify that the XDE JDBCdriverpath points to the DB2 client. To do this, follow these steps:

  1. Before running XDE, click Start > Run, and type regedit.exe.
  2. Go to the HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\XDE\AddIns\Data Modeler registry key, click the JdbcDriverPath value, and then verify that this path is valid and points to your db2java.zip file.
Documentation
134957

Help topics describing the Visual C++ functionality in Rational XDE are included as part of the XDE online Help system even though the VC++ functionality is not supported in this release of XDE. These topics are marked for technical preview. The technical preview release of XDE with VC++ functionality is available as a separate product. It will be included with XDE in a future major release.

242208

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

244074
When you add an existing model to a project, it is important to use the correct menu command to avoid possible model corruption. To add an existing model to a project, right-click the project node in the Solution Explorer and click Add > Add Existing Model. Do not use the Add Existing Item command because the subunits will not be copied into the project folder.
Installing and Uninstalling
58682
The administrator who installs Rational RequisitePro as part of the RequisitePro-XDE Integration should launch RequisitePro before a user without administrator permissions attempts to use RequisitePro from Rational XDE. Failing to do this may cause XDE to freeze.

223368 (65785)

Due to the installation image's large files, Rational recommends temporarily disabling the active scanning feature of your anti-virus software prior to installation. If you do not disable this feature, the installation could remain in an incomplete state.
236721

The following error occurs when an excessively long install pathname is specified:

Error 1320. The specified path is too long <pathname>

If the installation is then cancelled by clicking Cancel, the installer will exit, but the folder %INSTALLDIR%\RCSI\ and its contents will remain on the system. The RCSI folder and its contents should be deleted manually.

236727
The installer does not check to see if the destination install directory is a valid Windows directory. If a bad directory name is entered—for example, one with bad characters—the install may complete, but the installed product will probably not work correctly.
237629

If you have installed the Visual Studio .NET edition of XDE, followed by an install of XDE for Java, on the same system, the file associations for the .mdx and other modeling files are now associated with the XDE for Java product. If you uninstall the XDE for Java product, the icons associated with the file associations are uninstalled. This leaves the VS .NET edition of XDE functional, but some file icons are missing and are displayed with Windows generic icons.

Workaround: To restore the icons, reinstall the XDE for VS.NET product.

241162
Use of the Microsoft Windows XP "Run As" feature is not supported by the Rational Installer for Rational XDE version 2003. Please log in to an account with local admininstrative priviledges and run setup directly from this account.
447036
XDE will not work properly if it is installed into a folder on a network share. Use a local drive instead.
593408, (78359),
594321, (80161)
If you install both the Java and .NET editions of XDE on the same system, round-trip engineering tools for both editions appear in both editions' toolboxes. For example, C# tools and Java tools appear in both environments. However, the tools only work in the environment for which they are supplied.
596111, (83538)
When installing XDE, do not use the # character in your install path.
Internationalization
595383, (82143)
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).
236978
Installation of XDE will succeed only if the pathnames for Enterprise or Silent Install locations do not contain Japanese or multibyte characters. Similarly, if you copy the CD image to a share and attempt installation from such a path, the share name must not contain Japanese or double-byte characters. If you share the CD drive of a machine so that others can map to it to perform an install, the share name must not contain Japanese or double-byte characters.
240590
XDE cannot be installed into a path that includes extended characters.
449850

A Rational XDE diagram that contains Japanese or double-byte characters may not display correctly if you copy the diagram and paste it into Microsoft Word. (This is an issue for Japanese and English versions of Word.)

Workaround: Select all shapes, change the font for the selected shapes to an appropriate font, such as MS UI Gothic, and then copy and paste the shapes into Word (or another application).

595075
In Japanese versions of Rational XDE, some characters, such as backslashes, may not print as displayed in the diagram window if the appropriate language font set is not installed on the printer.
596709 (84595)
The « and » characters are not supported in Simplified Chinese. Therefore, when you add a shape to the drawing surface, the name in the Model Explorer is prefixed by two question marks (??). Two question marks are added with each subsequent edit of the name as well.
Patterns and Code Templates
47714

A pattern can have a template parameter of Unified Modeling Language (UML) Type Association and also contain Associations with the same names in the pattern’s Root Context. When the pattern is expanded, the Root Context’s Associations are correctly replaced with the template argument values in the target area, but validation errors are reported.

Workaround: In the Pattern Explorer, set the merge behavior on the template parameter’s Association Type element to Replace. However, a side-effect of the workaround is that the associations are duplicated when the pattern is reapplied.

135407

Bindings of external code templates in models from earlier versions of the product are not being upgraded correctly. After model upgrade, the external code template bindings are still functional in the upgraded model; however, the bindings are no longer suitable for use in situations where the path from the model to the external code template needs to be indirect. Typical situations where this occurs would be when a model is under configuration management and different users view the code template using different paths, or when the code template binding is copied from one model to another via using a pattern application.

Workaround: Find all of the bindings for external code templates in the upgraded model and open the binding for each (using the edit binding command); this will cause the binding to be restored to the proper format.

237735

View elements created by application of a pattern may duplicate on reapplication of that pattern.

Workaround: In the Pattern Explorer, set the merge hint on the diagram to Replace or Preserve to discard the existing diagram and create a new one or keep the existing one and add a new one (respectively), instead of trying to merge in changes.

50679

After a user applies a pattern that has a COM Callout or expands a COM Code Template, either in preview mode or in expansion/code generation mode, any modifications to the COM .dll file are not recognized.

Workaround: Modify the file as needed and then shut down or restart Rational XDE.

50899

When a user clicks Cancel in the Apply Pattern Wizard or the Apply Pattern dialog box, a dialog box appears to ask if the user wants to save the binding. Sometimes the binding is saved when No is selected.

Workaround: Perform an undo operation or delete the added binding.

50911

When exporting RAS files with the Export Wizard, a solution is listed as a project when the Export whole projects option is selected. However, a solution cannot be successfully exported.

Workaround: Export solutions by selecting the Export individual files (artifacts) option in the Export Wizard.

50964

If two developers each add a code template to the same method contained in a configuration-management-controlled model, the code templates can be checked in but not merged. Only one of the code templates can be merged and the other must be re-bound.

Workaround: Do not allow parallel addition of code templates to the same model elements.

134791

When applying a pattern that has an RXE .NET callout, messages to report errors such as missing assembly file, missing classes in assemblies, and exceptions thrown by callout code, are not reported.

Workaround: Add output messages to the callout code to report progress.

134833

The Pattern Explorer's Update Toolbox button does not update the properties for patterns that already appear in the Toolbox.

Workaround: To update an existing Toolbox pattern item, right-click the item in the Toolbox and click Delete. In the Pattern Explorer, click the pattern’s Toolbox node and click the Update Toolbox button in the Pattern Properties window.

134864

Reapply of a pattern does not remove elements added by a previous application of the pattern. For example, a pattern adds an operation with a scripted name, get<%=attributeParamName%>, and the first time the pattern is applied the template argument for the attributeParamName template parameter is Foo and the operation getFoo is added to the model. Then, the user changes the name of the attribute to Bar and reapplies the pattern. A new operation getBar is added, but the old getFoo is not removed.

Workaround: None.

135007

Most pattern callouts and constraints, when applicable, correctly add error messages to the Output window and an error message box. However, a few messages are instead added to the Task window.

Workaround: None for constraints. For callouts, add messages and specify that they appear in the output window.

135205

When upgrading models to this release, the ownership of the first generated or added URL linked to each nested bound collaboration changes. Ownership of the link transfers to the «Asset» package that owns the nested bound collaboration. Other URLs owned by the nested bound collaboration are not changed.

Workaround: Delete any URLs owned by bound collaborations before upgrading the model and manually add them back afterwards.

135133

Changes made to patterns properties (such as Expansion Enabled or Expand Nested Bindings) in the Properties window do not always update in the Pattern Properties window.

Workaround: Close and reopen the pattern in the Pattern Explorer.

230370

The Undo command does not work in the Pattern Explorer.

Workaround: Change focus to the Model Explorer or diagram window and then perform the undo operation.

237480

Some patterns and code template dialog boxes can display intermittent sizing problems, where a subcomponent of the dialog box becomes relatively smaller than the other components.

Workaround: These sizing problems can usually be corrected by resizing the internal components, by dragging the internal sash next to the component. Often, resizing the entire dialog box will also cause the internal components to resize correctly.

239096

When you validate the C# Pattern based on Design Patterns: Elements of Reusable Object-Oriented Software, the Facade Pattern contains one or more broken references.

Workaround: Manually redefine the stimulus for Facade/SubsystemClass participants.

58765

When applying the Iterator Pattern with selected values, errors will occur in the code.

Workaround: Apply the Iterator Pattern with default values, then rename the participants as needed.

51293, 135029

For models under configuration-management control, adding more than 16 code templates to the same model may cause the 17th element to appear twice in the element’s bindings when the model is checked-in and merged.

Workaround: Do not bind more than 16 code templates to a CM controlled model element if the model can potentially be merged.

595148

Diagrams included in the Root Context may contain elements that are duplicated in the target area diagram as a result of reapplying the pattern.

Workaround: In the Pattern Explorer, set the merge hint on the diagram to Replace or Preserve. The replace behavior discards the existing target diagram and replaces it with the pattern diagram. The preserve behavior adds an additional diagram to the target area.

Round-Trip Engineering
48440, 51029
Reserved words such as "class" in C# and Visual Basic are escaped in the code using language-specific syntax (@class, [Class]). In this release of Rational XDE, the escape syntax is not stored in the model. It is not possible to generate arbitrary escape characters (for example, @template) on first-time code generation.

If a Visual Basic .NET code model that was created in a previous release of Rational XDE contains names that are escaped keywords, then upgrading the model to the current release will require some extra manual steps. In Visual Basic .NET code, identifiers that would normally be keywords are still treated as identifiers if they are enclosed in square brackets.

For example, consider the following code:

Public Class [Sub]
  Dim [Event] As Integer
End Class

A class named Sub with a field named Event is defined, even though Sub and Event are normally keywords. In earlier releases of Rational XDE, when such code was synchronized with a model, the name of the model element contained any square brackets that were in the code. Modeling the above code would have resulted in a UML class with the name [Sub] and a UML attribute with the name [Event].

In the current release of Rational XDE, square brackets are automatically removed from names in the model (while leaving the square brackets in the code). Modeling the above code will now result in a UML class with the name Sub and a UML attribute with the name Event.

However, when upgrading an existing model that was created in an earlier release, the square brackets are not automatically stripped from names in the model during the upgrade process. When the model and code are first synchronized after upgrading, Rational XDE will report validation errors by adding Task items to the Task List window. Names with square brackets (such as [Sub] and [Event]) are not legal names in the model, and the synchronization will be stopped for this validation error.

To proceed, double-click the Task item to navigate to the problem in the Model Explorer and correct the name manually. Square brackets must be manually removed from the names in the model (such as changing [Sub] to Sub). Once these changes are made, synchronization can continue without validation errors.

51443
Model root contention can result from adding, moving, or deleting classifiers in subunits. For details and a workaround, see the guidelines under Round-Trip Engineering.
RXE (Patterns and Code Templates)
134740

As designed, the OnArgumentValue callout is invoked each time the user selects an argument value in the apply pattern tools. When the OnArgumentValue callout rejects the selected argument value, it is not added as an argument value for the template parameter. However, using OnArgumentValue does not consider the existing set of values to determine whether to add a new element to that set.

Workaround: Eliminate unwanted elements later in the pattern application by adding another callout, such as a PreExpand callout.

134761

When an OnBind callout or constraint fails, the pattern designer’s failure message text correctly appears in the Output window. However, the designer’s text fails to appear in the error message dialog box that opens when using the Apply Pattern dialog box. No error message appears when using the Apply Pattern Wizard. The Apply button is enabled in the Apply Pattern dialog box even though the OnBind evaluation has failed.

Workaround: None.

135180

Unable to successfully specify the name value for a Generated element in a PreApply callout. Without the name value, generated elements cannot be created.

Workaround: None.

Visual Trace
440352
If you are using the Visual Trace feature on Visual Studio .NET, and your application contains C# structures, the structures do not appear in the trace sequence diagram.
513464
Lifelines in Trace Sequence Diagram that do not have any messages to or from them, as a result of post-filtering operations, will not be included on a sequence diagram created through the Generate Sequence Diagram operation.
513630
When tracing ASP.NET applications, the first and second trace sequence diagrams produced following the startup of Visual Studio .NET may not include information to be able to browse to code. The third and subsequent trace sequence diagrams will have the appropriate information and the Browse Code menu item will be available from the trace sequence diagram.
514229

In Microsoft Visual Studio .NET 2003, selecting many C# classes from the same namespace (for example, 500 or more) in the Class Selection pane of the Visual Trace Wizard may result in exhausting virtual memory and various error messages. This problem is due to Microsoft SR#12455 defect 129398.

Workaround: Select fewer classes at one time.

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

(87752), (87858), 598186, 598244
Hotspots are currently not supported on activities contained within swimlanes.
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.

374617, 458596

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.
General XDE
14296
When you set the Rational XDE Toolbox to “float” using the Floating command on the Window menu, and then make the Toolbox smaller, the resized Toolbox does not contain a scroll-down button so you can access the other tabs that contain shapes.
25105
Attempting to use Rational XDE in Visual Studio .NET while logged in using a Guest account will result in a Package Load Failure Error dialog box. Dismissing the dialog box results in another error dialog box. This prevents you from using XDE with a Guest account. This is a known issue with Visual Studio .NET.
50796

During memory-intensive use of Rational XDE, the Java virtual machine (JVM) may produce an "OutOfMemoryError" error message.

Workaround: By default, the maximum size allowed for the JVM is 256 MB. The -Xmx option can be used to increase the memory available to the JVM. To increase the -Xmx option, go to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Rational Software\RJCB\JVMs\XdeJavascriptJvm

Modify the string value named JvmOptions (there should be other options present in this string value). You can increase the -Xmx$m option, where $ is the amount of memory, in megabytes, for the JVM to use. For example, to set it to 512 MB, change the string from -Xmx256m to -Xmx512m.

51429

When upgrading a model (.mdx file) from a past release of Rational XDE, you may see the
following error message, and the model fails to load: "Modeler Error: Failed to load model file <path>."

Workaround: Using the current release of Rational XDE, open the solution in which the model file resides. When you open the model, it will be upgraded and open correctly.

(57053), (26760), (26931)
Rational XDE will not print dashed lines correctly on some printers. This is noticeable for UML dependencies and messages.
58722

The Options dialog box may fail to open when the user clicks Tools > Options in Microsoft Visual Studio .NET 2002. The problem is that VS .NET 2002 supports only about 64 options pages. Each page is identified by a registry entry in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.0\ToolsOptionsPages

On a standard VS .NET installation, with XDE installed, almost all of the options pages are consumed. Installing additional third-party software may trigger the described defect.

Workarounds:

  • Uninstall third-party software.
  • Manually remove some of the registry entries for pages that are not used.
  • Upgrade to VS .NET 2003.
  • Check for a fix from Microsoft in future service packs for VS .NET 2002.
(71118)

When the zoom factor for a sequence diagram is set to 75% or 50%, you may encounter auto-sizing issues with the box at the top of a lifeline. A long name will appear elided in the box, rather than the box auto-sizing to accommodate the text.

Workaround: Adjust the zoom factor slightly and the box will correctly auto-size.

(73746), (73381)

When copying diagram content across Windows Terminal Server or Remote Desktop Connection to a local application, such as Microsoft Word, portions of the shapes and connectors are missing in the pasted image.

(77069, 77219, 83365, 84240, 84569)
You cannot open models by double-clicking on their files outside of XDE.
81963
Renaming a Toolbox shape with a name longer than 90 characters causes Rational XDE to crash while the Toolbox shapes are in icon view.
135018
In some cases, when you import a Rose model into XDE, an attribute's type specifiers (*, & , []) are removed. This can happen when aggregation is used and *, &, or [] is used on the member objects, or if the type itself is in the model and the .mdl file you are importing is from a recent release of Rose.
217562 (28247)
To be able to open an .rtf file after the file has been added to Rational XDE, you must edit the path name to the shell's Open command for the .rtf file. The path name must be enclosed in quotes.
227795 (78248)

Some Rational XDE operations are case-sensitive, which can lead to errors or problems with model dependencies. For example, if you delete a project and then re-create the project using the same name, but not the same case, the dependencies between models are lost.

Workaround: Use consistent capitalization when naming projects to prevent such problems.

236849

Attempting to save model templates with unsupported characters in the name (such as "ÿ" ALT+0255) will result in the New File dialog box disappearing without saving the model template file. No error is reported.

Workaround: Avoid using unsupported characters in model template file names.

239534

You can upgrade models created with previous versions of Rational XDE to Rational XDE version 2003. Before you begin the model upgrade process, verify that the read-only attribute is not set on any model files participating in the model upgrade process. For more information, see Rational XDE Help on upgrading models.

240108
Rational recommends that you not save models into the Miscellaneous Files folder.

240402

When you save a converted Rose model (.mdl) file, the Save As dialog box does not have the correct file extension specified for the target model. The correct file extension should be .mdx. If you continue saving without correcting the file extension, you will be prompted to save the converted .mdl file as an .mdx file. However, the saved .mdx file will not replace the .mdl file in the project as you would expect.

Workaround: Manually add the .mdx file to the project by using the Add Existing Model or Add Existing Item command.

240476

When editing the same model in two different instances of Visual Studio .NET, in parallel, a reload will not be performed when the model is changed in the other instance if the model being edited is part of a Miscellaneous Files project.

Workaround: Ensure that the model is part of a language project, not a Miscellaneous Files project.

511588
In some cases, when XDE tool windows (such as the Model Explorer) are docked with Visual Studio .NET tool windows (such as the Solution Explorer) and auto-hide is enabled, changing focus between the docked tool windows and other toolbars may cause Visual Studio or your computer to stop responding. This is a known issue with Visual Studio .NET.
514290
Do not delete or rename the model folder from within the Solution Explorer. If you do so, any associated subunit references will be invalid.
589837 (56712)

Changing line style of connector from oblique to rectilinear is not always optimal if the oblique line contains only right angles. Changing line style from oblique to rectilinear can reroute the connector, even when the line consists only of right angles. The line routing optimizes for shortest path and will reroute complex right-angled routings when performing the conversion.

Workaround: Manually adjust line routing to suit.

590299 (61999)
Rational XDE creates message connectors in a sequence diagram using the oblique style. Do not manually change the line style to rectilinear as the layout results are unpredictable.
592401 (75906)
When a call event is set with a reference operation (by dragging and dropping an operation onto a transition), the event name shown on the drawing surface or the Model Explorer is the reference operation name; the actual event name is displayed in the Property window. If the reference operation's name changes, the call event's displayed name in the drawing surface and Model Explorer also changes accordingly.
592414 (75944)

If you open a template model (for example, visualmodel.mdx or GettingStarted.mdx) directly from Windows Explorer, the file is immediately updated as a non-template model. Any models created from a template that was opened in this way will have the same model identifier (GUID), which will cause failures with certain cross-model references.

Workaround: Do not open template models in Windows Explorer. If you have already done so, reinstall the template model from the product CD.

Defects Fixed in this Release

The following table describes the defects fixed in this release. It lists all fixes in Rational XDE Version 2003.06.16, version 2003.06.15, version 2003.06.14, version 2003.06.13, version 2003.06.12, version 2003.06.01, and version 2003.06.00.

Category

ID

Description

Code Templates
86074
At code template expansion time, if there are errors, the error line number reported is not always correct.
86889

When binding a code template parameter with a string that contains a comma, the text after the comma is truncated. For example in a string such as "this.a=A, this.b=B", only "this.a=A" will be bound. The problem also occurs if semicolons are used in the string parameter.

Compare and Merge
66277

If you are comparing and merging a model with deeply nested elements, there may be the possibility of a crash (entire shell disappears) or a lockup. Deeply nested elements are those with over 80 levels of nesting. The compare and merge session can be invoked either directly, or by the ClearCase Type Manager. This problem is caused by the limited stack size of 256Kb provided by javaw.exe. For most users, this is an unlikely scenario. The following workaround is available for the out-of-stack-space problem:

  1. Save a copy of the original server executable, javaw.exe in the C:\Program Files\Rational\common\java\jre1.3.1_02 bin subdirectory.
  2. Change the thread stack size by running the following command at the command line in the bin subdirectory: editbin /stack:1048576 javaw.exe where 1048576 is the new stack size, specified in bytes. Increasing the stack size to 1048576 will allow the nesting of elements to a depth of well over 100 levels. If your models are nested deeper than this and you are still encountering the problem, consider organizing your model to avoid deep nesting, or further increase the stack size as necessary. Excessive increases of stack size (over 4MB) may result in performance degradation.
  3. You can confirm the new setting by running the Microsoft dumpbin utility, which is included with Microsoft Visual C++. Run the following command: dumpbin /headers javaw.exe In the output, the stack size appears in hexadecimal format on a line such as this: 100000 size of stack reserve.
83420

Rational XDE does not automatically resolve inter-model references to the new location of a referenced model, when the referenced model is copied (as opposed to moved) from one physical location to another. For example, suppose you have two models, Model A and Model B, in your development view and Model A references Model B (an inter-model reference). When you deliver the projects containing these models to the integration stream, the inter-model reference in Model A will continue to point to the version of Model B that is in the development stream. If the development and integration streams are not synchronized, this can cause errors or data loss.

89539
When one or more elements in a collection have been deleted in one compare/merge contributor, and more than one element has been added at the same location in another contributor, during the compare/merge, unless other rules (for example, parameter matching) are in effect, the new elements will be added to the merge result in the wrong order. However, no data is lost.

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
88055, 90056
Rational XDE will not launch if non-alpha numeric characters are used in the install path. No warning is given during installation.
69389
If you perform a Save All operation when the model contains new subunits that have not yet been saved, the project is saved first, and then the subunits are saved. However, saving the new subunits after the project has been saved updates the project again. Therefore, you need to save the project again.
69975

Adding a project from source control, or opening a file from source control from within Rational XDE sometimes results in an infinite loop.

73670

When adding a solution to source control, Visual Studio .NET first adds several temporary files to source control. Two of these files are sometimes left in the checked out state by Visual Studio .NET with ClearCase 4.2.

86549
If you merge models where a shape in a diagram should be resized to fit the results of the merge, the change in size is not visible immediately: It doesn't matter what you choose during the merge for (PositionalGeneralView) Extent.
87013

If there is a conflict between two stereotypes in a merge session, the stereotypes will be removed in the merged model, and you will not be notified. This situation will arise if two users are working on a model unit in parallel and each changes the stereotype of the same model element to different values. The first user to submit the changes to the repository will encounter no problems. However, the second user to submit changes will trigger a merge operation. During this operation, the two stereotypes will be discarded silently.

87414
When comparing and merging model files from within Rational ClearCase, ClearCase attempts to start the Rational XDE Compare/Merge capability. You may receive the following error if you are missing the registry key that is normally created by the ClearCase installation program:
"Missing > extended naming suffix after -extNamingSuffix parameter."
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
84695
To do a compare and sync, the schema of the databases or the DDLs being compared must be the same. The compare and sync will not display the differences if the schema names are different.
84604

Foreign key has a keylist property in the Property browser, which can be updated so that it references the column that you want.

  1. Create 3 tables (database not relevant at this point).
  2. Draw a relationship between the tables such that 2 tables are parents of the other one.
  3. Add a primary key to the 2 parent tables.
    This should migrate the primary key and add two separate foreign keys to the child table.
  4. Select one of the key constraints in the child table. In the Property browser, change the name of the column to point to the same columns as the other foreign key.
85065

Use the following steps to multiselect tables under a single package:

  1. Sort the elements in the Model Explorer, either by Element Type or by Stereotype to group all elements together (for example, tables to tables, views to views).
  2. Select the first table in the Model Explorer, and then go to the last table. Hold down the Shift key and click the last table in the Model Explorer, which selects all of the tables needed for transformation.

Note: If you need to select tables that are not adjacent to each other, hold the Ctrl key instead of the Shift key as you click each table you want to select.

85718

View columns that contain reserved special functions cannot be forward engineered.

90627
The Data Modeler Options dialog box (Tools > Options > Rational XDE > Data Modeler) does not function. Alternative procedures must be used to set the Data Modeler options for your model.
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
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.

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

Obsolete documentation for Adding Template Arguments for Template Parameters
Installing and Uninstalling
86673

When upgrading from Rational XDE version 2002 to Rational XDE version 2002 Release 2, you may receive a message in the Install Summary window related to the file ntvauth.dll. This message can be safely ignored and will not be seen on future upgrades.

87239
When installing Rational XDE, do not put a backslash ("\") at the end of the install path (for example, C:\Program Files\Rational\). This will result in incomplete installation of the product. Workaround: Specify the path without a trailing "\" character (for example, C:\Program Files\Rational) to ensure successful installation.
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. 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"

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

Patterns Support
65804

The Pattern Property window's single-line text fields do not support the use of the Enter or Tab keys to indicate edit completion.

85844

When adding a new model to adding a pattern asset to it, the Use Model for Asset option in the Add Pattern Asset dialog box does not work. Instead of launching the Project Selection dialog box so that you can specify the project under which to wish to create the new model, the pattern is created under the currently selected model.

86081

The multiplicity values of Invoker, Command, Receiver, ConcreteCommand and State are not set in the GoF/C# Command pattern.

86082

The multiplicity values of the Visitor, ConcreteVisitor, Element, ConcreteElement, and ObjectStructure are not set in the GoF/C# Visitor pattern.

90669

Patterns menus are not updated when you install Rational XDE Professional on a machine on which Rational XDE Modeler Edition was previously installed.

RequisitePro Integration
59126, 238444
Using the Rational RequisitePro-XDE integration caused JVM error messages when closing Rational XDE.
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.

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.

Shapes
56264, 66330

Clicking on the visibility indicator of an attribute or operation on a shape in a diagram will invoke a pick list that can be used to change that element's visibility. The "hot spot" that detects the mouse click and invokes the pick list is slightly misaligned on component shapes, however.

77353

When entering an operation name, certain syntax is not properly accepted in the class shape or the Model Explorer. For example, the name entered as "<%aClass.getName()%>" is parsed as "<%aClass.getName() : %>", which will lead to subsequent errors upon pattern expansion.

Visual Studio .NET Integration
23100
Visual C# indexers are not modeled in this release. You can freely use them in the source code. XDE will not modify them.
31058

There are synchronization problems with using drag and drop in the Model Explorer to change the Visual C# namespace of an existing class.

55830, 69828
When synchronizing member functions, you may get a synchronization error if you rename more than one function parameter or reorder the parameters.
56589
A nested class whose name is identical to its containing class will cause a synchronization error.
58359

You cannot customize toolbox using Reset Toolbox.

77786, 73269

Under some conditions, using the Auto Hide feature with the Model Explorer tool window may cause the Visual Studio .NET user interface to become unresponsive.

83297
Selecting F1 while the Code Properties window (a Rational XDE round-trip engineering window) is in focus does not call the Rational context-sensitive Help window as expected. Instead, the Visual Studio .NET Help topic for the Properties window is displayed.
90593
Text containing an ampersand (&) in the Model Documentation window causes the subsequent model documentation to be truncated when generated in the code, from the line containing the ampersand through the end of the model documentation.
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.

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

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

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

Web Modeling (ASP.NET)
90112

After code exists for an element in the model, if you change the value of its ImplementationFile property and then synchronize or generate code for the element, errors are displayed in the Task List.

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.
(84246), (86198), 596528, 597457

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

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

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

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.