Rational® XDETM - .NET Edition

Release Notes

Version 2002 Release 2

Part Number: 800-025696-000


Copyright

Copyright ©2002, Rational Software Corporation. All rights reserved.

This software contains proprietary and confidential information of Rational and its suppliers. Use, disclosure or reproduction is prohibited without the prior express written consent of Rational.

Legal Notices

About this Document

The Rational XDE Release Notes contains important information you will need to install and use Rational XDE - .NET Edition. It is important to review this document because it describes: 

Note: The printed version of this document does not include the listing of Known Issues. In order to provide the most up-to-date information possible at release time, this information is included only in the online version of the Rational XDE Release Notes. The online version is installed with the Rational XDE product, and you can also access it directly from your product CD. In addition, to be sure that you have the absolute latest available information, we recommend that you download the Rational XDE Release Notes from http://www.rational.net/XDEcenter.

Contents

About this Document
Welcome to Rational XDE
Joining the Rational Developer Network
What Is the Rational Developer Network? 
How to Register
What's New in This Release
Hardware and Software Guidelines
Hardware Guidelines
Software Guidelines
Rational XDE Packaging and Features
Packaging Information
Visual Modeling Features
Data Modeling Features
Team Development and Configuration Management Features 
Web Publishing and Reporting Features
Visual C# Modeling and Round-Trip Engineering Features
Development Accelerators 
Integrated Use Case Management
RUP Configuration for .NET Developers
Getting Help and More Information
Compatibility Issues
Rational Administrator and Rational Rose
Rational XDE with Rational RequisitePro
Rational XDE with Rational ClearCase
Installing and Uninstalling Rational XDE
Installation Issues
Installing Rational XDE
Uninstalling Rational XDE
Getting Started with Rational XDE
Starting Rational XDE
Using the Getting Started Model
Creating a New Model in an Existing Project
Creating a New Model of a Visual C# Project
Understanding Rational XDE Tool Windows
Upgrading and Migrating Models to Rational XDE v2002 Release 2
Frequently Asked Questions (FAQ)
Restrictions and Guidelines
General
Cut/Copy/Paste Behavior
Sequence Diagrams
UML Interfaces 
Development Accelerators
Web Publishing and Reporting
Configuration Management
Compare and Merge 
Visual C# Round-Trip Engineering
Sharing Models through E-mail
Known Rational XDE Issues
Issues Fixed in This Release
Contacting Rational Technical Support

Welcome to Rational XDE

We at Rational Software believe that this release is the beginning of a new and vital chapter in rapid application development and visual modeling. You now have one of the most powerful tools for designing, communicating, and documenting all phases of software development integrated with the same tools you use to develop the applications and systems you build. This is seamless integration at its best.  Whether you work within highly structured processes and require durable, long-lived models, or you are an extreme programmer and modeler using lightweight, disposable models, this is the tool flexible enough, intuitive enough, scalable enough, and synchronized enough to become an indispensable part of what you do.

Rational XDE lets you build a rich, highly scalable semantic representation of your entire system, from system architecture to its static and dynamic structure. Plus it's completely integrated with the tools you use to edit, debug, and test. Automatic synchronization of your system’s model and code means you are always able to see and understand the solution you're developing without forcing you to focus on the tools you're using. What’s more, Rational XDE fully leverages the effort you put into modeling your architecture and design because it can generate large portions of your application through automatic pattern expansion and Rational Development Accelerators™. If you do not already have an architectural model, Rational XDE can reverse engineer your existing application into a rich, visual model, allowing you to understand and modify your system at any level of abstraction or detail you choose.

So thank you for joining us. We are confident you'll not only like what you see, but what you can do.

Back to Contents

Joining the Rational Developer Network

What is the Rational Developer Network?

The Rational Developer Network is a Web site that extends the reach of your development team with the expertise of an online community, providing practical information and a forum for exchanging ideas and best practices. This site benefits you and your team by helping you to:

Available 24x7, this Web site aggregates articles, book excerpts, scripts, hooks, triggers, models, plug-ins, patches, and other artifacts that help you use the Rational tools in your project environment. Content is updated weekly and is created by Rational experts, customers, and partners such as the IEEE Computer Society and Addison-Wesley. By participating in online discussions, you can connect with development professionals all over the world and leverage their experience. Also, you can access quality Web-based training on concepts and tools by Rational University or technical training by our partner Digital Think.

With the exception of Web-based training, all of these resources are available to you and each member of your team, at no cost, as a part of your active maintenance agreement. For more information about the Rational Developer Network, visit http://www.rational.com/services/rdn.  

How to Register

It's easy to register. Simply visit http://www.rational.net/register, enter your account number, and set up a username and password. You can find your account number on the shipping information and invoices that were sent to you. If you have trouble finding your account number, call Technical Support Licensing at (800) 433-5444, Option 3. Please have your sales order number, PO number, or host ID available for authentication purposes.

Back to Contents

What's New in This Release 

Frictionless Design and Development 

Unleash the Power of Your Patterns

Instant UML/Assisted Modeling

Data Modeling

Web Publishing and Reporting

Enhanced Internationalization Support

Back to Contents

Hardware and Software Guidelines

Hardware Guidelines

The following table provides minimum and recommended system configuration requirements for Rational XDE. 

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. 

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.

Rational XDE runs under the minimum configuration; however enterprise-level development is enhanced when resources conform to the recommended configuration.

Processor Pentium II-class processor, 450 MHz. Recommended: Pentium-III class processor, 700 MHz or higher
Available RAM Minimum: 256 MB. Recommended: 512 MB (Modeler package only: Minimum: 128 MB; Recommended: 256 MB)
Available Disk Space Minimum: 400 MB for installation drive, 50 MB for workspace. Recommended: 2-4 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

Back to Contents

Software Guidelines

Operating Systems

The following operating systems are tested and supported: Windows 2000 Professional, Service Pack 2; Windows XP Professional; Windows NT 4.0 Workstation Service Pack 6a.

See Installation Issues for more information regarding unsupported operating systems.

Operating System Languages

Level 2 support for German, French, Italian, Swedish, Japanese, Simplified Chinese 
Level 1 support for Dutch, Hebrew, Traditional Chinese, and Korean 

Microsoft Visual Studio .NET You must properly install Visual Studio .NET, with .NET Framework Service Pack 1, before installing Rational XDE. If you have not yet done so, please refer to the specific platform requirements for Visual Studio .NET, which are available from Microsoft. See Installation Issues for information regarding other versions of  Visual Studio .NET.
Internet Browser Internet Explorer 5.5, Service Pack 2, or higher must be installed on your system. However, you can use other browsers, such as Netscape 6.0, to view published models.
Web publishing and reporting Web publishing and reporting requires the Java Plug-in, downloadable from the Sun Web site at http://java.sun.com/products.
Rational RequisitePro To use the Integrated Use Case Management (IUCM) integration of Rational RequisitePro and Rational XDE, you must have RequisitePro, Version 2002.05.20 installed on your system. See Installation Issues for more information.
Configuration Management Supports ClearCase 4.2, ClearCase v.2002.05.00, ClearCase LT v.2001A.04.00, ClearCase LT v.2002.05.00, Microsoft Visual SourceSafe 6.0c. Supports the SCC interface; therefore, configuration management systems conforming to the SCC interface are expected to be compatible with Rational XDE.

ClearCase installation should include all mandatory patches for your version of ClearCase. Current patch requirements are as follows:

  • For ClearCase 4.2, patches 11 and 12
  • For ClearCase LT v.2001A.04.00, patch 7
  • For ClearCase v.2002.05.00, patches 4 and 5
  • For ClearCase LT v.2002.05.00, no patches

To verify the latest patch information for your version of ClearCase, go to http://www.rational.com/support/downloadcenter

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

Back to Contents

Rational XDE Packaging and Features

Packaging Information

Rational XDE v2002 Release 2 is available in several packaging options for use with Microsoft Visual Studio .NET:

Notes

Back to Contents

Visual Modeling Features

Rational XDE empowers you to create comprehensive, flexible UML models from within a world-class integrated development environment.

Back to Contents

Data Modeling Features

Rational XDE provides data modeling features that allow you to build, model, and design your database, and map it to your application and architectural models. Having all of your information in one place and one language helps to open up the lines of communication across teams and enables them to build applications that map directly to the database. With Rational XDE, you can model your database from scratch and generate the database based on the model, reverse engineer an existing database into a data model, or compare and synchronize your data model with your existing database.

Rational XDE data modeling capabilities support the following databases:

Back to Contents

Team Development and Configuration Management Features

Rational XDE works in conjunction with supported configuration management software to provide source control, versioning, and backup capabilities. (See Hardware and Software Guidelines for information on supported configuration management software.)

You can divide models into multiple files (called storage units) to make it easier to work with large models, as well as to facilitate working with teams and configuration management systems. On-demand storage unit loading lets you access model elements without knowing whether they are currently loaded; the unit simply loads automatically when you access an element that requires it.

The following model elements can be made into storage units on their own or in combination with other model elements:

If you add storage units to a configuration management system, such as Rational ClearCase, the storage units become controlled units. You can set your preferences to automatically check out controlled units when you edit them, or to automatically add newly created storage units to your configuration management system.

Using Rational XDE compare and merge capabilities, you can view the differences and conflicts among model or storage unit files, manually or automatically resolve conflicts, and then merge the files to produce a single output model. This becomes especially important when your team development workflows allow more that one person to work on the same controlled units at the same time.

Back to Contents

Web Publishing and Reporting Features

Rational XDE provides web publishing capabilities that let you create and publish a navigable, HTML-based view of your model and generate various types of reports in HTML format. 

A published model is a portable snapshot of a model that you can view, share, and navigate using your preferred web browser. You can also choose from a number of out-of-the-box, pre-defined report templates to generate HTML-based reports, including:

These Web publishing and reporting features let you easily share information across roles and organizations, without requiring stakeholders to have Rational XDE on their desktops.

Back to Contents

Visual C# Modeling and Round-trip Engineering Features

Rational XDE provides fully integrated Visual C# round-trip engineering capabilities in the Microsoft Visual Studio .NET environment. This includes code generation, reverse engineering, and automatic round-trip engineering, all of which are accessible from the Solution Explorer, the Class View, the XDE Model Explorer, and XDE diagrams. 

All XDE functionality is tightly integrated into Visual Studio .NET:

Back to Contents

Development Accelerators

Rational XDE includes support for patterns and code templates, the key building blocks for software development accelerators. Fully integrated and traceable pattern support lets you create, capture, package, apply, and re-apply design patterns. Perhaps the most important pattern-support feature is UML-to-UML transformation, which allows you to add new UML elements to a model, as well as modify existing UML elements in a model. 

In addition, you can easily specify your own patterns using the Patterns Toolkit, which provides everything you need to find, create, edit, apply, and document patterns in your model. The Patterns Toolkit includes:

Using these tools, patterns content providers can create patterns that:

Code template support lets you automatically generate code for operation bodies, which is a manual process in tools other than Rational XDE. Code templates automate the tedious tasks of writing and rewriting the same code multiple times. In addition, code templates are integrated with patterns, and can be customized with parameters or scripts. You can even apply patterns that attach code templates to any pattern-created or pattern-modified element in your model.

Back to Contents

Integrated Use Case Management

Integrated Use Case Management enhances the comprehensive capabilities of Rational XDE use-case modeling with the powerful requirements management capabilities in Rational RequisitePro. This integration lets you associate your Rational XDE model and its use cases to requirements in a RequisitePro project.

For information on starting and using Rational XDE with the Rational RequisitePro integration, see Rational XDE with Rational RequisitePro in the Compatibility section of the Release Notes. 

For more information, see the Integrated Use Case Management topic, which is in the Working with Use-Case Diagrams Help book in the Rational XDE Help, or open the Integration Use Case Management Help, which is located on the Tools > Rational RequisitePro menu.

Back to Contents

RUP Configuration for .NET Developers

When you purchase Rational XDE v2002 Release 2, you also receive RUP Configuration for Microsoft .NET Developers (RCND). 

The Rational Unified Process, or RUP, product is a software engineering process. It provides a disciplined approach to assigning tasks and responsibilities within a development organization. Its goal is to ensure the production of high-quality software that meets the needs of its end users within a predictable schedule and budget. 

RCND is a straightforward, lightweight process configuration of the Rational Unified Process (RUP) that has been specifically customized to address the needs of software developers. It provides guidance to architects and developers on the essential requirements, analysis and design, and implementation activities. The goal of the RCND is to provide a repeatable process to enable software developers to develop high-quality applications faster, more reliably, and more consistently. 

For more information on RCND, check the Release Notes in xdeinstalldir\RationalUnifiedProcess.rcnd\Readme_First.html.

Back to Contents

Getting Help and More Information

In addition to the Rational XDE Release Notes, you will find complete documentation for Rational XDE .NET Edition in the form of fully integrated online Help, including context-sensitive Help.

To access Rational XDE online Help, do one of the following:

You can also access links to additional XDE Resources, including the Rational Developer Network, XDE Knowledge Center (which includes links to the latest Release Notes), the XDE Tutorial, and other information. Access these XDE Resources in one of the following ways:

  1. Click Help > Search.
  2. Look for Rational XDE Resources.
  1. Access the Rational XDE Help book.
  2. Expand the Modeling with Rational XDE Software book.
  3. Click the Rational XDE Resources topic and follow the links to the resources you want.

Note: Indexing and filtering capabilities for Rational XDE Help have been added to this release.

Back to Contents

Compatibility Issues

Rational Administrator and Rational Rose

If you have used the Rational Administrator to set up a Rational project that includes Rational Rose models, and you subsequently migrate your Rose models to Rational XDE, the Rational project in the Administrator will continue to show your registered project as containing the Rose models, even though they have become obsolete. See Migrating Rational Rose Models into Rational XDE for more information on Rational Rose to Rational XDE migration.

Rational XDE with Rational RequisitePro (Integrated Use Case Management) 

If you have Rational RequisitePro and intend to use the Integrated Use Case Management (IUCM) Integration with Rational XDE, be sure to install RequisitePro, Version 2002.05.20.

For each model with which you intend to use this integration, you must set the model's AppliedProfiles property to RequisitePro:

  1. In the Model Explorer, select the model.
  2. In the Properties pane, type RequisitePro in the AppliedProfiles property.

Setting the AppliedProfiles property automatically creates the necessary default packages in the model (Component View, Deployment View, Logical View, Use Case View) and also adds the Rational RequisitePro integration to the Rational XDE Tools menu.

To start the Rational RequisitePro/XDE integration, which lets you associate your model and its use cases to requirements in a RequisitePro project, click Tools > Rational RequisitePro in Rational XDE. 

Back to Contents

Rational XDE with Rational ClearCase

Setting ClearCase Options

When running Rational XDE with Rational ClearCase, activating the options described in the following table is recommended. To access these options, click Tools > Options; then, in the Options dialog box, click Source Control > SCC Provider, and then click Advanced...

Preserve file modified time on checkin
Preserve file modified time on checkout
Activate these options so that, if you check out a file that is currently open in an editor, you will not be prompted to reload the file from disk because it appears to have changed. This option is highly recommended. 
Note: ClearCase 4.2 and ClearCase LT v.2001.A.04.00 do not display these options; however, the setting is enabled by their latest patches.
Checkin even if identical Activate this option to avoid a Cannot check in identical  files warning when checking in items for the first time. Note that this warning is harmless (the items are, in fact, checked in), but may cause confusion. However, activating this option can allow you to inadvertently check in an identical version of a file without getting a warning, so choose the setting of this option that best suits you.
Save copy of file with .keep extension Activate to make it easy to locate an earlier file version, which can be helpful in recovery from user error. This option is recommended.

Working with Multiple Snapshot Views

If you are using ClearCase 4.2 or ClearCase LT v.2001A.04.00 and you have more than one snapshot view open on the same stream, then the changes you make to the stream in one view will not be seen in the other views unless you update those other views as well.

Comparing and Merging Rational XDE Models Using Rational ClearCase

To be able to compare and merge Rational XDE model and subunit files directly in Rational ClearCase, you must configure Rational XDE as a ClearCase type manager. For instructions, see the Rational XDE online Help  topic, Configuring XDE as the ClearCase Type Manager

Back to Contents

Installing and Uninstalling Rational XDE

Installation Issues

Back to Contents

Installing Rational XDE

Follow these steps to download and install Rational XDE,

  1. Close all applications that are running, especially any version of Rational XDE.
  2. Ensure that you have administrator privileges on the system where you are installing Rational XDE. You will not be able to complete installation if you are logged in with a userid that does not have full administrative access.
  3. Load the Rational XDE product CD.
  4. Locate, then double-click setup.exe to begin installation.
  5. Click Next when alerted to close all applications.
  6. In the Choose Product dialog box, click the product to install, and then click Next.
  7. Read the License Agreement and indicate acceptance using the appropriate option button.
  8. Click Next to continue or Cancel, if you do not accept the terms of the agreement.
  9. From Select Configuration, accept the default Typical configuration and installation location.
  10. Acknowledge the installation by clicking Next in the Confirmation dialog box. 
    Installation continues until all files and components have been registered and copied to your system, and an Error Summary lists any errors encountered during installation.
    Note: Rational XDE online Help is installed as the last step in the installation process. The process may seem to stop for up to 2 minutes while this is happening. 
  11. If you are prompted to do so, restart Windows and log in again as administrator to complete the installation.

Back to Contents

Uninstalling Rational XDE

You can uninstall Rational XDE by completing a conventional uninstall through Add/Remove Programs in Control Panel. Alternatively, use the following procedure:

  1. Click Start > Programs > Rational XDE > Rational Software Installed Product Information.
  2. From the list of installed software, select Rational XDE and click Add/Remove.
  3. From the Add/Remove dialog box, select Rational XDE and click Change/Remove.

The Rational Installer does not remove files that have been created or modified since the installation of the product. There are two directories of particular interest where these files may reside: 

Where:

If you uninstall Rational XDE, we recommend that, prior to re-installing Rational XDE, you either rename or delete these directories, which may be left behind after uninstall. Do not delete the directories without first ensuring that any user-created files are backed up, as needed. In addition, if more than one user has used this installation of Rational XDE, you should clean up each user's application data.

Back to Contents

Getting Started with Rational XDE

Starting Rational XDE

Rational XDE is fully integrated with Visual Studio .NET. To start Rational XDE, simply start Visual Studio .NET.

Using the Getting Started Model

The Getting Started model, installed with Rational XDE, is a model template that can help you begin modeling quickly by providing a model structure that conforms to industry best practices. You can add, remove, or rearrange model elements as required for your application. 

The Getting Started model includes separate packages for modeling your system's use cases, design, and deployment. As you become familiar with Rational XDE, you will discover that Rational XDE supports multiple models. You may choose to maintain separate physical models for use cases, design, and deployment, rather than using the packages provided in the model template. In addition, if you are an application developer, you will want to maintain multiple code models, which maintain an implementation-level view of your system and keep your code and models synchronized automatically.

Follow these steps to create and open a new instance of the Getting Started model:

  1. Click File > New > File.
  2. Click Rational XDE in the left pane, click Getting Started in the right pane, and then click Open.
  3. Click File > Save Modeln As... to save the new instance of the model.  
  4. Type the name for the model, and save it in an appropriate project folder.

Back to Contents

Creating a New Model in an Existing Project

Once installation is complete, Rational XDE is fully integrated in the Visual Studio .NET environment, and you are ready to create a new model and familiarize yourself with the many features that Rational XDE provides.

Models are stored in files that you manage just as you manage any files in Visual Studio .NET. You can add new or existing model files to your solutions and projects. To create a new model file in an existing project:

  1. Right-click a solution or a project in the Solution Explorer.
  2. Click Add > Add New Item
  3. From the Add New Item dialog box, click the Rational XDE folder in the Categories list, and select Blank Model or Getting Started as the Template.
  4. You can add existing models to your solution and projects by using Add > Add Existing Item.

Back to Contents

Creating a New Model of a Visual C# Project

Follow these steps to create a model of the code in an existing Visual C# project:

  1. From the Solution Explorer, select a Visual C# project in the Solution Explorer
  2. Right-click the project name and click Synchronize. Rational XDE creates a model of the Visual C# project.

The name of the model is the same as the name of the project and will typically contain two top-level UML packages; that is, one package with the same name as the project and stereotyped as <<namespace>>, and the other package named Artifacts. You use this model to round-trip engineer your project.  Any new classes that are added to your code are also added to the model when you synchronize the project. Conversely, any new UML classes that are added to the model are also added to the code as a result of synchronization. Classes are generated in the namespace that corresponds to the UML <<namespace>> package that contains the class.

Back to Contents

Understanding Rational XDE Tool Windows

Rational XDE adds the following windows to the Visual Studio .NET shell:

 These tool windows are fully sizeable and dockable within Visual Studio .NET. You access these windows by clicking View > Other Windows.

Back to Contents

Upgrading and Migrating Models to Rational XDE v2002 Release 2

Upgrading Models to Rational XDE v2002 Release 2

Rational XDE v2002 Release 2 is compatible with models created in Rational XDE v2002. This means that models and files created in Rational XDE v2002 can be viewed and edited in Rational XDE v2002 Release 2. However, before you view and edit a model in Rational XDE v2002 Release 2 that was created in Rational XDE v2002, the model file and all related model files must go through an automatic model conversion process. 

Important:  The automatic model conversion process allows you to save backup copies of your Rational XDE v2002 models before you upgrade. This is highly recommended because Rational XDE v2002 Release 2 models are not downward compatible with Rational XDE v2002. Once a model is upgraded to Rational XDE v2002 Release 2, it cannot be opened in Rational XDE v2002. 

Migrating Rational Rose Models into Rational XDE

You can convert existing Rational Rose models (.mdl files) to Rational XDE models by opening them in Rational XDE and saving them to the new model file (.mdx) format. When you do this, almost all basic model elements and characteristics are converted to Rational XDE equivalents. For example, most of the properties and settings that appear in Rational Rose specifications have similar properties or tagged values in Rational XDE that you can view in the Property Browser. On the other hand, the mapping between C++ or Visual Basic language elements and Rational Rose models are not preserved in Rational XDE.

For basic instructions, as well as details on how Rational Rose model elements map to Rational XDE model elements, see Importing Rational Rose Models in the Rational XDE online Help.

Notes:

Back to Contents

Frequently Asked Questions (FAQ)

Q: I've started Visual Studio .NET. How do I know Rational XDE is installed?

A: In the main menu, click Tools > Options. If Rational XDE is installed, you will see a folder named Rational XDE in the left pane of the options dialog.  Alternatively, on the Windows Start menu, click Programs > Rational XDE Your Edition > Rational Software Installed Product Information. A window appears that shows the versions of all installed Rational products.

Q: How do I get to the XDE modeling functionality?

A: The user interface for XDE modeling can be found in these windows:

Q: How do I start UML modeling?

A: You begin by creating and adding XDE model files to your .NET solution. Model files, like all files, can be added directly to the solution or to any project in the solution. Once a model file has been added, you can double-click the model file in the Solution Explorer to open it. In the Model Explorer tool window, you can now begin constructing your model by adding UML diagrams, packages, classes, etc. Simply select a model in the Model Explorer, right-click, and then click Add UML and Add Diagram.

Q: How do XDE and my project code work together?

A: Through the process known as synchronization, Rational XDE can synchronize your Visual C# source code with a UML model. (Note that Visual Basic and C++ are not supported in this release.) The steps are simple: In the Solution Explorer, select the project, and then click Synchronize on the Solution Explorer toolbar. Or, you can right-click the project in the Solution Explorer, and then click Synchronize on the shortcut menu. Rational XDE will automatically create a new UML model by the same name as your project. This model will include UML packages that represent the namespaces in your project and UML classes that represent the Visual C# classes in your code.

Q: How are the code changes I make in my project reflected in my models and my diagrams?

A: Simply select the project in the Solution Explorer, then right-click Synchronize.

Q: How do I generate code for a UML class I create in a diagram?

A: The project model described above is the home for all UML items you want to synchronize with your code. Here are the steps:

  1. Determine in which Visual C# project you want your class to reside.
  2. Use the Synchronize command to create a model for that project (described above).
  3. Move your UML class to the package in the project model that represents the target namespace for your class. You can add new namespace packages to the project model by creating UML packages stereotyped as <<namespace>>. 
  4. Right-click the class and click Synchronize.

Q: Can there ever be conflicts between the code and my models?

A: Yes. Conflicts may appear in the Visual Studio .NET Task List window as a result of the Synchronize command. Right-click on a conflict task to resolve it. You have two choices:

Q: Do I always have to remember to click the Synchronize button?

A: If you always want to keep your model up-to-date with your code, consider enabling the Automatic Synchronization feature. Click Tools > Options > Rational XDE > Round-Trip Engineering and select the Automatic Synchronization checkbox. This dialog box lets you trigger synchronization on File > Save events, or when you change focus between code and model.

Q: Can I navigate back and forth between my code and the UML items that represent the code?

A: Yes. In the Model Explorer, select a model item and right-click Browse Code. This will take you to the code that implements the selected model item. You can also right-click on a declaration in a source code file and click Browse Model. This will take you to the corresponding item in the XDE Model Explorer tool window. Browse Model is also available on nodes in the Visual Studio .NET Class View tool window.

Q: How does XDE work with Visual SourceSafe?

A: An XDE model file is like any other file in the solution. If you add your solution to Visual SourceSafe, your XDE model files are added as well. When you use synchronization, XDE follows all of the source control options that you have set for your solution. To set source control options, click Tools > Options > Source Control.

Note that, in Visual Studio .NET, files that are added to the Miscellaneous Files folder in the solution are never added to source control.

Q: Is there any way to see a model of a .NET assembly created from a C++ .NET or Visual Basic .NET project?

A: Yes. When your Visual C# project references .NET assemblies, synchronizing your Visual C# project will create a shallow model of the binary assemblies that are referenced. These assemblies appear in the Miscellaneous Files folder in the Solution Explorer. Be sure to enable the appearance of this folder by clicking Tools > Options > Environment > Documents,  and then selecting the Show Miscellaneous files in Solution Explorer checkbox. Once you have a shallow reference model, you can make it a deep reference model by right-clicking the reference model in the Model Explorer and clicking Synchronize. You can use classes from reference models on diagrams in your Visual C# model. For example, you can model your Visual C# class so that it inherits from a class in an assembly that was compiled with Visual Basic .NET.

Back to Contents

Restrictions and Guidelines

General

Back to Contents

Cut/Copy/Paste Behavior

The results of drag-and-drop and cut/copy/paste actions vary depending on the types of items involved in the original selection and in the target. The results also vary depending on whether or not the target is in the same model as the original selection. As background to understanding these variations, an understanding of the following terminology is helpful: 

Cross-model Considerations

Pasting of view elements is currently disabled; however, you can create a new view element of any model element by dragging the model element from the model explorer onto the diagram surface. 

Intra-model Considerations

Back to Contents

Sequence Diagrams

Sequence diagrams behave differently depending on their owner in the model. Sequence diagrams must be owned by an Interaction, which in turn must be owned either by a collaboration or a collaboration instance. Collaborations are role-based, whereas collaboration instances are instance-based or object- based. The simplest way to create a sequence diagram with the required interaction is to do the following:

  1. In the Model Explorer, right-click an element, such as a package.
  2. Click Add Diagram > Sequence:Instance or Sequence:Role

Note: When a sequence diagram's interaction is owned by a collaboration instance, the lifelines dropped on the drawing surface are objects. 

Another way to create a sequence diagram is to first create a collaboration, then create an Interaction, and finally, create a sequence diagram. At this point, any lifelines dropped on the diagram will be classifier roles.

Back to Contents

UML Interfaces

You can view a UML Interface on a diagram as a rectangle (that is, the shape of a class) or as a circle. You can toggle between the two representations by changing the UseClassShape property in the Property Browser.

Back to Contents

Development Accelerators

The Modeler package of Rational XDE includes patterns capabilities, but does not include the GoF patterns. 

To import the GoF/C# pattern model (GoFPatternLibrary.mdx) into your Rational XDE project, click File > Import. This extracts the model from the RAS file (GoF.ras) and places it in the target location of your choice. The model includes attached documentation files that provide background information on the patterns. The imported GoF/C# pattern model is writeable, which means that you can alter the pattern definition for your needs. To restore the model defaults, re-import the RAS file to another location.

Note: In order to preserve the updated links for your chosen target location, be sure to save the model when you first import it.

Back to Contents

Web Publishing and Reporting

Java Plug-in

The web publishing and reporting 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 reports. If you have not already downloaded and installed the plug-in, you are prompted to do so the first time you use a web publishing or reporting capability 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 and reporting.

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

Because, publishing models requires significant free disk space, use the following guidelines when publishing:

Back to Contents

Configuration Management

Using ClearCase Dynamic Views with Rational XDE

To use ClearCase Dynamic Views, it is necessary to allow UNC paths to be trusted. This security setting can only be set by a user with Admin privileges. If you receive the following Microsoft Development Environment message when trying to use a ClearCase Dynamic view, click the Help button in the message box, and follow the recommended steps to change the security settings: 

Note: The project location is not fully trusted by the .NET runtime. This is usually because it is either a network share or mapped to a network share on the local machine. If the output path is under the project location, your code will not execute as fully trusted and you may receive unexpected security exceptions.

Partitioning Models into Subunits

When you create an XDE model and partition it into subunits, the subunits are automatically added to the project. However, if you move a model into a project, you will have to manually add the subunits to the project before you can perform configuration management operations. To do this, select all of the subunits, then right-click and select Add to Source Control....

Using ClearCase View Servers with Rational XDE

To be able to compare and merge Rational XDE model and subunit files directly in Rational Clearcase, you must configure Rational XDE as a ClearCase type manager. For instructions, see the Rational XDE online Help  topic, Configuring XDE as the ClearCase Type Manager

Back to Contents

Compare and Merge

Comparing and Merging Models

If you close Rational XDE while a Merge session is in progress, the Merge session will be terminated without displaying a warning. If all conflicts are resolved, the result will be the same as when ending a Merge session normally. If there are still unresolved conflicts, then the Merge session is abandoned and any intermediate results are discarded.

Comparing and Merging Round-Trip Engineering Projects that Show Unfamiliar Differences or Conflicts

When comparing and merging round-trip engineering projects, you may see differences or conflicts that do not appear to be related to any changes that you have made. These may appear in one or more of the following tagged value overrides (TVOs):

The differences and conflicts appear specifically in Value properties in the Comparative Property Explorer. The difference is usually a string value that is interpreted by a programming language round-trip engineering feature that you are using. Although these elements are not visible in the Model Explorer and most likely were not modified by you or your team members, they may have been modified internally, following a modification of round-trip engineering model elements. The round-trip engineering feature specifically recognizes these properties after a merge, and regenerates them as necessary.

You can safely resolve the resulting differences or conflicts by accepting the default resolution provided in a non-conflicting difference, or by resolving conflicts using any of the contributors. To regenerate these by round-trip engineering, always synchronize the project immediately after merging.

Back to Contents

Visual C# Round-Trip Engineering

Back to Contents

Sharing Models Through E-mail

If you want to share models with others on an informal basis, you can send models through email or place them on a shared directory. This is easy to do, as long as you take proper steps to ensure that the recipient receives all files that are part of the model(s).

Depending on the storage unit policy you have selected, your model can consist of a single file with an .mdx extension, or it may be composed of several files, or storage units. These storage units are located in a directory with the same simple name as the model file. For example, if you have a model called CommunicationLayer, you will have a corresponding model file called CommunicationLayer.mdx. You may also find a folder called CommunicationLayer, containing additional storage units for the model. 

Follow these steps to informally share a model: 

  1. Create a folder or ZIP file to contain the model files you will share. A ZIP file is recommended in order to reduce file sizes for email transmission.
  2. Locate the .mdx file in the file system and drag the .mdx file's enclosing folder onto the ZIP file icon. 
  3. When the Winzip Add dialog box appears, click Add to add the .mdx file to the archive. 
  4. If your model contains storage units, drag the folder containing its subunits to the ZIP file and Add them to the archive as well. Note that, if the folder exists, it will have the same name as your model file, but without the .mdx suffix.
  5. Ensure that you did not include any Rational XDE index files (.idx file extension) or  .ratl_comp_root files in the zip file.
  6. For each additional model that you wish to share, follow steps 2 through 5.
  7. Send an email with the ZIP file to the intended recipient.

Upon receiving the ZIP file, do one of the following:

Back to Contents

Known Rational XDE Issues

Category

ID

Description

 

Installation 

62179 If you install Rational XDE on a system that has Rational Suites installed, the License Administrator launches during the installation process. Workaround: Close the administrator and continue.
64475, 65999 If you are installing Rational XDE over Microsoft Visual Studio .NET 7.0 with VSIP, you must install Rational XDE before installing VSIP. Otherwise, Rational XDE will not be accessible to all instances of Visual Studio.Net 7.0 on your system.
65785 Due to the installation image's large zip 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.
77069, 77219, 83365, 84240, 84569 If you install more than one version of Rational XDE on the same system, you cannot open model files by double-clicking in Windows Explorer. Workaround: Open the files in Explorer by using the Open with command, or open from within Rational XDE.
78359, 80161 If you install both Rational XDE Professional v2002, Java Platform Edition and Rational XDE Professional v2002, .NET Edition 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 (C# in .NET and Java in Java Edition).
79815, 83348 Because of the deep product directory structure, the length of the base installation path (default = C:\Program Files\Rational) must not exceed 60 characters or installation errors will be encountered as the full path plus file name length of some files will exceed the 255 character limit for Windows.
86673, 86674 When upgrading from Rational XDE v2002 to Rational XDE v2002 Release 2, you may receive the following message in the Install Summary window: 
The file "ntvauth.dll" which is being installed into directory "C:\Program Files\Rational\common", already exists on this system in directory "C:\Program Files\Rational\jintegra\bin". If the two versions are not compatible, features may not operate correctly. See the Release Notes after installation completes.  Release Notes will be located at "C:\Program Files\Rational\doc"

This message can be safely ignored and will not be seen on future upgrades.

86696, 86864 If you are upgrading to Rational XDE v2002 Release 2 - .NET Edition, you must also upgrade any pre-existing version of Rational XDE - Java Platform Edition that resides on the same system. If you do not do this, Rational XDE v2002 Release 2 - .NET Edition will start, but you will not be able to edit or modify models.
87239, 87466 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.

 

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. Workaround: Make your namespace changes in the code instead of the model, and then use the Synchronize command.
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. Workaround: Restart Visual Studio .NET.
61839 The Synchronize command may appear as a context menu command at times when the command is unavailable. You can only synchronize model items that reside in the project model (that is, a model added to a project whose name is identical to the project).
67934 Deletion of an enumeration in the model may leave trailing semicolons (;) in the code after synchronization
67984 There may be errors when synchronizing a class that has UML relations to a class that has been deleted from the model.
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. Workaround: Click the pushpin icon on the title bar of the Model Explorer window.
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.
81989 Do not enter more than 500 characters in the Property Browser
84059 Folders for controlled units do not appear in the Solution Explorer for Blank (Basic) solutions. This behavior is caused by the fact that Basic Solution projects in Visual Studio .NET have a flat directory structure. Workaround: No workaround is required. Even though the structure is not reflected in the Solution Explorer, the files point to the correct physical files on your system.
84318, 84800 Names may disappear from tabs on diagrams, form editor, and code editor when many diagrams or documents are open at once. Workaround: Close some diagrams or documents.
87122, 87214 Model Files managed under the Visual Studio .NET Miscellaneous folder may not be saved. Rational XDE users should add model files to either a .NET solution or a .NET project. If you use any of the XDE file storage options (for example, Automatic-All, Automatic-Typical), avoid accessing those models from the Miscellaneous folder in the Solution Explorer because Rational XDE is not aware when subunit files of Miscellaneous models are dirty. Therefore, Rational XDE may allow you to close one of these models without prompting you to save it, resulting in loss of your unsaved data.
 

General

28247 To be able to open a .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.
73056 If you share files and allow more than one user to work on the same files without benefit of supported configuration management software, Rational XDE does not provide file change notification, and update conflicts can easily occur. Workaround: If more than one user is working with the same model files, it is strongly recommended to use a configuration management system, such as Rational ClearCase, to avoid conflicts due to model file updates. 
74602 An extended delay when loading XDE for the first time (30 seconds or more longer than to load another application) may be due to network configuration issues. If the system is disconnected from the LAN delays are not apparent. Under network configurations which would result in a delay when trying to access other systems (for example, mounting a network server)  XDE will experience a delay when loading for the first time only. Workaround: Disconnect the system from the LAN, or resolve the network configuration issues.
75807 When Rational XDE is running, Internet Explorer running within Visual Studio .NET cannot use the Java Plugin. If you try to start a Java-enabled web page, an error message will appear.  Workaround: Run a separate instance of Internet Explorer, or start the web page in a separate instance of  Visual Studio .NET.

If you try to start Rational XDE when a Java-enabled web page is running, an error message will be displayed. Workaround:  Shut down and re-open Visual Studio .NET,  or run Rational XDE in a separate instance of Visual Studio .NET.

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 Browser. If the reference operation's name changes, the call event's displayed name in the drawing surface and Model Explorer also changes accordingly.
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
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.
84278 The Location Registry modeling option, which is meant to maintain references between models, if the models are moved, does not function properly. Workaround: Change the names of the following files, which will cause the Broken References dialog box to appear, allowing you to repair the model and the location registry file.
\Documents and Settings\ userid\My Documents\XDE Workspace\.ratl_comp_root
\Documents and Settings\ userid\My Documents\XDE Workspace\.ratl_comp_root_README_DO_NOT_DELETE
\Program Files\Rational\common\rgy\ratl_comp_local 

Notes

  • If you are running on Windows NT, the directory structure will be different. In that case, you will need to search for the file names on your system.
  • The period (.) at the beginning of the first two file names indicates that these are hidden files. If you cannot see them in Windows Explorer, click Tools > Folder Options, and then click the View tab, where you can set whether or not hidden files are visible.
84956 There is no message on upgrade/save of read-only models. Because the models are being converted to a new version, a new file is being created. If you want to preserve the original read-only status, create a backup or set the converted file’s property to read-only.
 

Internationalization

82143 When downloading the Java plug-in required for web publishing and reporting, if you are running a Japanese OS, you must choose the International Version of JRE from the Sun website (for Netscape), or select the appropriate Locale (for Internet Explorer). See defect 71502 for information on the Java plugin requirement.
81375, 82027, 83353, 84288 Do not install Rational XDE in a directory with double-byte or extended characters in the path name (for example, using Japanese characters). It will not function if installed in this way.
82395 Rather than defaulting to the system font, the default font for Rational XDE is Tahoma, which does not display properly on an Japanese operating system. Workaround: Update the default Rational XDE font to match your system font. To do this, click Tools > Options > Rational XDE > Default Font, and choose System from the font list.
 

85402, 85986, 86420

These related defects have the following symptoms:
  • A copy or cut and paste between Rational XDE and another application (for example, MS Word) with a non-default character sometimes displays erroneous characters when pasted. Workarounds: On Windows 2000, select the elements to be copied and then manually set the font using the Font Selection drop down menu on the command bar. On Windows NT4, English characters display correctly. There is no workaround for non-English characters at this time. On Windows NT4 with Hebrew enabled, both English and non-English characters display incorrectly, and there is no workaround at this time. 
  • Text from non-default character sets do not appear in elements of published models (for example, class names, relationship names, etc.). Workarounds: On Windows 2000, select the elements to be published and then manually set the font using the Font Selection drop down menu on the command bar. On Windows NT4, English characters display correctly. There is no workaround for non-English characters at this time. On Windows NT4 with Hebrew enabled, both English and non-English characters display incorrectly, and there is no workaround at this time. 
  • On Windows NT4 and Windows 2000, you may not be able to assign a new character set by setting the font from the Rational XDE Preference dialog box.
Printing 57053, 26760, 26931 Rational XDE will not print dashed lines correctly on some printers. This is noticeable for UML dependencies and messages.

 

Shapes

55216 If you use the High Contrast display option for Windows 2000 Accessibility, the cursor is not visible in Rational XDE diagrams.
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.
57151 When attempting to extend a selection (for example, by using Ctrl+ click) on a shape nested within a composite shape, this gesture clears the previous selections, rather than extending the selection. 

Workaround 1: Select all shapes using Ctrl + A (or a marquee select), then unselect the unwanted shapes using Ctrl+Click.
Workaround 2: To multiple-select nested shapes, first select any nested shape. Next, while pressing the Shift key, click any empty space inside the parent shape. This will select all shapes, including the parent. Finally, while pressing the Ctrl key, click the parent shape. This will de-select the parent shape, while leaving all nested shapes selected.

61999, 73809 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
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. Workaround: Invoke the pick list by clicking slightly to the right of the visibility indicator, or simply change the visibility in the Property Browser.
71118 When the zoom factor for a sequence diagram is set to 75% or 50%, you may encounter autosizing issues with the box at the top of a lifeline. A long name will appear elided in the box, rather than the box autosizing to accommodate the text. Workaround: Adjust the zoom factor slightly and the box will correctly autosize.
73746 When copying diagram contents 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.
76890 On a class shape that is shown as a graphical stereotype, the stereotype icon (shape) can disappear. Workaround: Turn AutoSize on and off again.
77167 Position of Destroy messages sometimes cannot be moved down on a lifeline. 
Workarounds
  • Move the Destroy message above another message on the same lifeline, causing the lifeline to grow vertically because the Destroy message is no longer the last message on the lifeline. Then, move the Destroy message down. 
  • Increase the height of the lifeline by changing the value of its height property.
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. Workaround: Select the operation in the Model Explorer, and then edit the Name property as desired in the Properties window.

Sequence Diagrams

57053

Lifeline does not print on RICOH printer. The dashed vertical line of a lifeline reportedly does not print correctly on a RICOH Aficio AP4500 PCL printer. Workaround: This defect has not been reported on other printers. A printer driver problem has not been ruled out at this time.
 

Data Modeling

84153 Open Specification Options in shortcut menu in the Model Explorer does not function for the following objects: Triggers, Key Constraints, Dependency Relationship, Tablespace Container.
84695, 84704 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, 85295 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.
84855, 84893 Data modeler menu items are missing after Help is brought up. Workaround: Click anywhere to remove focus from the table, and then reset the focus to the table and right-click. The items return to the menu.
85065, 85066 Use the following steps to multi-select 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.

85574, 85576 Domain in not a supported data modeling stereotype in the Pattern Asset dialog box.
85718, 85777 View columns that contain reserved special functions cannot be forward engineered. Workaround: Make the view user-defined by checking the User-defined checkbox on the General tab in the View editor before attempting to forward engineer the view.

 

Web Publishing and Reporting

 

71502, 79902, 85461, 85797, 85867

The publishing/reporting function requires the Java Plug-in. The Java Plug-in is not included in the Rational XDE installation. If you attempt to use the publishing/reporting capabilities before you have the plug-in, one of these will happen:
  • The Java Plug-in installation wizard starts and leads you through the installation process. (Internet Explorer)
  • You are connected to the Sun Web site to download the Java Plug-in. (Netscape Navigator) 

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

Although the applet is signed by Rational, it could happen that the default security settings for the Java Plug-in version 1.4 do not allow read permission. Workaround: Use a text editor, such as Notepad, to change the .java.policy file to grant local applets read permission on all files, as follows:.

  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.

Notes: 

  • If you cannot connect to the internet, you will not receive any notification regarding the plug-in, and you will get errors when using publishing and reporting capabilities. 
  • If you run on Windows NT, you must close XDE before you can download the plug-in.
  • You must have Administrator rights to download and install the Java plug-in.
76887, 86208 If you use Netscape 6.0 as your default browser, when you click Review in the Publish Model or Generate Model Report dialog boxes, 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.
80155, 86188 In Windows XP, displaying the thumbnail view while browsing for a directory from the Publish Model dialog box causes an error. Workaround: Do not use thumbnail view.
82834, 86175 When you publish a model or generate a report, the corresponding dialog boxes remain open but allow you to continue to work on the model drawing surface. Working on the model while these processes are running may adversely affect either or both the model and the publishing or reporting results. Workaround: While a model is being published or a report is being generated, do not make any changes to the model.
84246, 86198 A model element name that contains an single quote (‘) is truncated at that single quote in the published model tree. Workaround: Do not use a single quote in a model element name.
85176, 86419 In rare cases, when you publish multiple models successively, you may get the following message, which prevents you from performing any further actions in the model: A read action is open on behalf of client ‘RSE Client’. Workaround: Exit and restart Rational XDE.
85508 You cannot display published models using UNC paths. The Java tree will not load as expected. Workarounds: 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.
87286, 87521 The Getting Started sample model file may not publish completely when published more than once during the same Rational XDE session. Workaround: If you want to publish the Getting Started model a second time, close and reopen Rational XDE to create a new session.
87337, 87519

 

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

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

 

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

 

Model Compare and Merge  

66277, 84727
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: (To change the thread stack size, you must have the Microsoft "editbin" utility, which is included with Microsoft Visual C++.) This command-line utility allows you to modify object files, executable files, and dynamic link libraries (DLLs). For more information on the editbin utility, see the Microsoft Visual C++ documentation. 
  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
73443 If you merge two or more contributors, and one of the contributors contains a storage unit whose file name differs from its name in other contributors, the name change may not be detected. Example: If you merge two versions of a model, M1, which has a package, P1, containing classes C1 and C2,.and one of the contributor models has renamed the storage unit file associated with one of the classes, that renaming will not be detected during the Merge operation. As a result, the merged model will be unable to resolve to the storage unit of class C1, and you will need to resolve the broken reference manually after the merge.

Note: This issue occurs only when the renamed storage unit is immediately below a package and when the renamed file is not participating in this particular merge session, such as during a Deliver operation, where a separate merge session occurs for each individual storage unit with conflicts to be resolved. This issue will not occur if you initiate the merge session manually and merge the entire model in a single merge session. In this case, the package and its contained classes are both loaded during the merge, so the changed storage unit name is detected.

76252, 26812 When running on Windows XP and executing a Compare and Merge command, sometimes the window panes or progress bar does not render properly on the screen. Workaround: Minimize and then restore the Visual Studio .NET application. When you restore the application, the Compare and Merge windows will be drawn correctly.
83797 On rare occasions, you may encounter the following error message when initiating a compare/merge session:  
The process cannot access the file because it is being used by another process.

This message indicates that the Rational XDE Type Manager is already accessing the file due to some other operation. This can happen if the Type Manager hung during an earlier operation. Workaround:  End the xdetypemgr.exe process in the Windows Task Manager, and then restart your compare/merge session.

81867, 82392 When you have installed more than one version of Rational XDE, any ClearCase operations that starts Rational XDE as a type manager (for example, when you Deliver or Rebase and a merge is performed on a controlled unit) will start the most recently installed version of Rational XDE, regardless of the version used to make the changes that are being merged. Workaround: Complete the merge operation using the version of Rational XDE that is started.
83420, 85328 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. Workarounds: When accessing the models in the integration view, set the Location Registry for both models to the integration view.  When accessing the models in the development view (for example, when rebasing from the integration stream), set the Location Registry for both models to point to the development view in which you will be working. To set the Location Registry, highlight the model in the Model Explorer; then, on the main menu, click Modeling > Location Registry. See the Rational XDE Help for more information.
86007 Icons in the Comparative Model Explorer might not reset to indicate the appropriate language when you alternate between comparing generated model artifacts from a C# model with comparing generated model artifacts from a Java model in the same Compare and Merge session.  Workaround: Close the Compare-Merge session and then start a new session, if you are working with models that generate source in different programming languages.
86962 Help topics are hidden when a Compare-Merge session is active in Rational XDE. Workaround: Drag the Compare Merge windows so you can see the topics.

 

Configuration Management 

59891, 82737 When you add many items to source control at one time, such as by adding a solution to source control, and your source control system is Rational ClearCase, you may be prompted more than once to specify an activity for the operation. In general, you should use the same activity throughout the operation. Workaround: Select the same activity each time you are prompted.
63229 If you exclude a unit from the Solution Explorer, its corresponding model element remains in the Model Explorer. Performing configuration management operations on a unit that has been excluded from the Solution Explorer is not supported.
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, 84473, 85155 Adding a project from source control, or opening a file from source control from within Rational XDE sometimes results in an infinite loop. Workaround: When the Browse for Folder dialog box is displayed, do not press Cancel. Instead, select a folder that is neither in a view location nor in the My Computer root directory and press OK. You will get an error message stating that the project must be in a view. When you press OK to release the message, you exit the loop as well.
73670, 83293 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. Workaround: Depending on your ClearCase settings, you may need to manually undo the checkouts on these files through ClearCase itself, rather than through XDE in order to perform a Deliver operation.
73678, 83190 The second time you open a solution after having started Visual Studio .NET, Visual Studio .NET
may not recognize the solution as being under source control, even if it is.
Workaround: Follow these steps when opening any solution subsequent to the first one that you open in Visual Studio .NET, if the solution is under source control:

1. Select File >Source Control >Open From Source Control.
2. Browse to the folder containing the *.sln file, and select OK.
3. Select Overwrite.
4. Select the *.sln file, and the solution will open properly.

77190, 26937 If you choose to discard in-memory changes when performing an on-demand checkout, you may see a dialog box prompting you to either overwrite the file you were editing or to save it as a new file. However, when you choose to discard the changes, this dialog box is inappropriate. Clicking on either button will result in the following error message: 

Modeler error: Save; details: the operation is invalid because the containing model has been closed

Workaround: You can ignore the error message because the in-memory changes have, in fact, been discarded.

77632 To use ClearCase Dynamic Views, allow UNC paths to be trusted. This security setting can only be set by a user with Admin privileges. If you receive the following Microsoft Development Environment message when trying to use a ClearCase Dynamic view, click the Help button in the message box, and follow the recommended steps to change the security settings: 

The project location is not fully trusted by the .NET runtime. This is usually because it is either a network share or mapped to a network share on the local machine. If the output path is under the project location, your code will not execute as fully trusted and you may receive unexpected security exceptions. 

76766, 83292, (CMBU00060282) If you are working with Rational XDE and Rational ClearCase using dynamic views and a checkin or checkout operation triggers a merge operation, and you proceed with the merge, Visual Studio .NET may lock. Workaround: Click Cancel if a checkin or checkout operation prompts you for a merge, and then execute the checkin or checkout command outside the shell, such as from a ClearCase Explorer window.

Notes

  • This problem can occur when more than one user is sharing a single ClearCase stream, or if a single user has more than one view open on a single stream. In either case, a file can be changed in a view different from the one you are using in XDE. If you then check in a file and ClearCase finds that there is a more recent version of that file in the repository than the one on which you based your changes, a merge will be triggered. At that point, the shell will lock because the thread performing the checkin operation is the same thread that is called to perform the merge, even though the checkin is not yet complete. This can also occur on checkout if you have made changes to a local copy of an older version of the file being checked out, which also triggers a merge.
  • ClearCase Rebase and Deliver operations are not affected by this limitation because the execution thread used to perform the Rebase or Deliver operation is not executed from within the Visual Studio .NET environment.
  • This issue is caused by a ClearCase problem, which is being tracked as CMBU00060282.
76995 The configuration management settings for the When checked-in items are edited... option, when selected from within XDE, do not take affect until you restart Rational XDE.
78137, 85149 (CMBU00061232) Some temporary files created by Visual Studio .NET are not added to source control while performing a Deliver from Stream, and warning messages are displayed. You can ignore these messages. This is a known ClearCase defect. Please contact the ClearCase Technical Support group at Rational Customer Service and ask for the status of defect CMBU00061232.
83195 When you add a solution to source control using ClearCase 4.2 or 4.2 LT, even if you set your ClearCase options to allow identical checkins, you will still receive warnings if you check in identical files. Workaround: You can safely ignore these warning messages.
83403, 85853 If you attempt to use File > Source Control > Open From Source Control to open a solution that is under source control, you may see the following error: 
This project (Project2.sln) cannot be opened from source control probably because it is a Visual Studio 6.0 solution. If this solution was created with a previous version of Visual Studio, you may be able to open it from source control using that version of Visual Studio, and then use Visual Studio.NET to open that local copy.

Workaround: When using Rational ClearCase with Rational XDE - .NET Edition, use File > Open Solution to open any solution which is under source control. 

86573, 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.
85144, 86863 If you are working with Microsoft Visual SourceSafe and perform an edit operation that causes a checkout of a Rational XDE model file, and if there is a newer version of the file in the repository, you will encounter an error. When you dismiss the dialog box, the operation you performed does not take effect because the newer version of the file just obtained from the repository is loaded instead. At this point, you will again need to perform the operation that triggered the checkout in the first place. Workaround: Perform a Get latest version request manually, before performing an operation that will trigger a checkout.
87013, 87030 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. Workaround: Add the stereotype back to the model element.
87414, 87699 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

Workarounds: Have ClearCase create the registry key now, or create it manually yourself.

To have ClearCase create the registry key:

  1. Click Start > Settings > Control Panel.
  2. Double-click the ClearCase icon to display the ClearCase Properties dialog box.
  3. On the MVFS tab, delete the contents of the Extended Naming Suffix text box, which activates the Apply button.
  4. Enter @@ in the Extended Naming Suffix text box, and click Apply to cause ClearCase to create the appropriate registry key. 

To manually create the registry key, go to the registry, and do one of the following:

  • For ClearCase LT, set the value of HKLM\SOFTWARE\Atria\ClearCase\CurrentVersion\xnsuffix to @@.
  • For ClearCase, set the value of HKLM\SOFTWARE\Atria\ClearCase\CurrentVersion\HistoryModeSuffix to @@.
Code Templates 86074, 86592 At code template expansion time, if there are errors, the error line number reported is not always correct.
86671, 86715 One of the key techniques for customizing patterns is to copy and paste a pattern (for example, a GoF pattern) into one of your projects and extend it from there. If Code Templates is not in the Applied Profiles of the model to which you are pasting the pattern, the code templates will not be copied or pasted.  Workaround: Add Code Templates to the Applied Profiles of the destination model before doing the copy.
86889, 86900  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. Workaround: use some other delimiter and convert that delimiter to the one you want within the code template body, or, where feasible, use multiple template parameters.

 

Patterns Support

60921, 86589 When the name of a template parameter type is changed in the Model Explorer, the Pattern Explorer correctly updates the label on the type node to reflect the change, but fails to update the name of the type in the template parameter's Pattern Properties dialog box. Workaround: Close and re-open the pattern in the Pattern Explorer.
61225 Expansion engine does not support multiple expansion locations and uses the same location for all elements.
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. Workaround: Use Control+Tab or the mouse to move the cursor to a different field or window after editing the field.
67452 Scriptlets in constraints are not processed. Workaround: Implement the constraint using the expansion engine callout mechanism.
67854 The Patterns Constraint Editor does not support the construction of some complex constraints.
67993 There is no mechanism to automatically import pattern stereotypes into new models.
68900, 71909 All template arguments must originate from the same model. You cannot specify template argument values from multiple models in the same application of a pattern.
68901 Patterns have no control over the way in which an element is merged into an ordered collection.
68902 Patterns cannot set a property or tagged value to its default value.
68903 Subtractive patterns are not supported. This means that patterns can add and modify model elements (change their properties), but they cannot remove elements from a model.
74802 The application of a pattern, followed by the opening of a diagram created by the pattern's expansion, may place the system in a state in which two Undo actions, rather than one, are required to undo the effects of the pattern application.
76218, 86591 The unbinding of a corrupt binding does not always display the Unbind dialog box if one or more other bindings are left on the bound item. Workaround: Unbind all other bindings on the bound element.
81387, 86588 Deleting a template parameter that has been specified as the default expansion location leaves the model in an incorrect and unexpandable state. 
81714, 86586 If a pattern contains a diagram, that diagram can be created in a given context, but it cannot be merged. If you apply the pattern more than once using the same expansion location the merge result of the two pattern applications corrupts the pattern.  Workaround: For multiple pattern applications (not re-apply), from the Pattern Explorer window, set the Merge property on the diagram to Preserve. This will cause a new instance of the diagram to be created each time the pattern is applied, rather than merging with the existing diagram.
85844, 86587 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. Workaround: Create a model as a Pattern Asset outside of this dialog box by changing an asset's root context to its owning model in the Pattern Explorer.
86884, 86898 If you apply a pattern to a model element that has an existing binding, the existing binding is lost and two copies of the binding from the pattern appear. This only occurs if both code templates are external code templates, that is, stored external to the model. Workaround: Convert one or both of the external code templates to internal code templates.

Back to Contents

Issues Fixed in This Release 

Category

ID

Description

 

Installation

69285, 69383

Do not attempt to install Rational XDE on NT4. The installation fails.
63472, 76358, 85474 Rational XDE will fail to install if your system path is too long. When Rational XDE is installed, it adds approximately 124 characters to your system path. The Microsoft Windows Operating Systems have limits on the length of the system path, and if your path is already very long, these additional 124 characters may not be successfully added. 

Publishing/Reporting

69642

Publishing models and generating reports not supported

 

Configuration Management

76766

If are working with Rational XDE and Rational ClearCase and a checkin or checkout operation triggers a merge operation, and you proceed with the merge, Visual Studio .NET will lock. Workaround: Click Cancel if a checkin or checkout operation prompts you for a merge, then execute the checkin or checkout command outside Visual Studio .NET, such as from a ClearCase Explorer window.

Notes

  • This problem can occur when more than one user is sharing a single ClearCase stream, or if a single user has more than one view open on a single stream. In either case, a file can be changed in a view different from the one you are using in XDE. If you then check in a file and ClearCase finds that there is a more recent version of that file in the repository than the one on which you based your changes, a merge will be triggered. At that point, Visual Studio .NET will lock because the thread performing the checkin operation is the same thread that is called to perform the merge, even though the checkin is not yet complete. This can also occur on checkout if you have made changes to a local copy of an older version of the file being checked out, which also triggers a merge.
  • Note that ClearCase Rebase and Deliver operations are not affected by this limitation because the execution thread used to perform the Rebase or Deliver operation is not spawned from inside Visual Studio .NET.
78555 When ClearCase initiates a Rational XDE merge operation  (for example, when you perform a Deliver or Rebase operation), the merge operation may fail if the model consists of more than one storage unit. Workarounds: Manually merge the model before delivering or rebasing so that ClearCase does not need initiate the merge. Another alternative is to ensure that the model consists of a single storage unit.

 Shapes

77166

Messages gravitate toward lifeline header. Workaround: Start messages lower on the lifeline

Patterns

68906, 80218, 80255

Pattern migration is only supported via RAS Import/Export.

 

Code Templates

77387, 77093 If you create a file using Tools > Code Templates > Create File while the Clearcase integration is on, you you are prompted to add elements to source control. If you clear the Keep Checked Out option, you will get Clearcase errors and the element will be hijacked. Workaround: Do not clear the Keep Checked Out option.
74976 If you generate code from an operation that has code templates attached to it, copy that code to another operation without code templates attached to it, and then synchronize, the code originating from the code templates will be removed.
76193, 76254 If you paste to a new location a model element that is attached to code templates whose parameters are model elements, the parameter values will require repair; you will need to manually edit the bindings.
 

Patterns Support

63182  Expansion engine supports only a straight copy when you copy elements. It is not possible to augment the copied operation(s) with additional features such as stereotype, parameters, etc.
68899  The Pattern Explorer does not support multi-select and drag & drop capabilities.
68904  If a pattern user applies a pattern that adds code templates to a method and the pattern designer then adds additional code templates to the pattern definition, the new code templates are not added to the method when the pattern user reapplies the pattern.
68906  Pattern migration is only supported via RAS Import/Export.
70142 Expansion engine callout code implemented in COM or Java cannot be identified using a pathname or a ProgID. Workaround: Java classes must be identified by class name and the class must be visible in the classpath. COM classes must be identified by a registered CLSID.
73977 The Apply Pattern Wizard is enabled for, but not always usable with, frozen models. Workaround: The usage of patterns with non-modifiable models is pattern-specific. Patterns can never be expanded to non-modifiable models; however some patterns do allow argument values to be supplied from such models.
Visual Studio .NET Integration

62653

Refresh status doesn't work in the Model Explorer. A checkmark symbol appears next to the .mdx file in the Solution Explorer, but not next to the top-level model element in the Model Explorer. Workaround: If you right-click on the top-level model element in the model explorer, it still behaves as if it is checked out, it just does not have the appropriate symbol.
62941 You will get a synchronization error if you rename a constructor operation in a model without renaming the class as well.

Back to Contents

Contacting Rational Technical Support

If you have questions about installing, using, or maintaining this product, contact Rational Technical Support as follows:

Your Location Telephone Facsimile E-mail
North America

(800) 433-5444
(toll free)

(408) 863-4000
Cupertino, CA

(781) 676-2460
Lexington, MA

support@rational.com
Europe, Middle East, Africa

+ 31 (0) 20 4546 200
Netherlands

+31 (0) 20-4545-201
Netherlands

support@europe.rational.com
Asia Pacific

+61-2-9419-0111
Australia

+61-2-9419-0123
Australia

support@apac.rational.com

When you contact Rational Technical Support, please be prepared to supply the following information:

Back to Contents

Legal Notices

TRADEMARKS

Rational, Rational Software Corporation,  Rational the e-development company, Rational Developer Network, ClearCase, ClearCase Attache, ClearCase MultiSite, ClearDDTS, ClearQuest, ClearQuest MultiSite, DDTS, Object Testing, Object-Oriented Recording, ObjecTime & Design, Objectory, PerformanceStudio, Rational ProjectConsole, PureCoverage, PureDDTS, PureLink, Purify, Purify'd, Quantify, Rational Apex, Rational CRC, Rational Rose, Rational Suite, Rational Summit, Rational Visual Test, Requisite, RequisitePro, RUP, SiteCheck, SoDA, TestFactory, TestFoundation, TestMate, The Rational Watch, AnalystStudio, ClearGuide, ClearTrack, Connexis, e-Development Accelerators, ObjecTime, Rational Dashboard, Rational PerformanceArchitect, Rational Process Workbench, Rational Suite AnalystStudio, Rational Suite ContentStudio, Rational Suite Enterprise, Rational Suite ManagerStudio, Rational Unified Process, XDE, SiteLoad, TestStudio, VADS, among others, are either trademarks or registered trademarks of Rational Software Corporation in the United States and/or in other countries. All other names are used for identification purposes only, and are trademarks or registered trademarks of their respective companies.

Microsoft, the Microsoft logo, Active Accessibility, Active Client, Active Desktop, Active Directory, ActiveMovie, Active Platform, ActiveStore, ActiveSync, ActiveX, Ask Maxwell, Authenticode, AutoSum, BackOffice, the BackOffice logo, bCentral, BizTalk, Bookshelf, ClearType, CodeView, DataTips, Developer Studio, Direct3D, DirectAnimation, DirectDraw, DirectInput, DirectX, DirectXJ, DoubleSpace, DriveSpace, FrontPage, Funstone, Genuine Microsoft Products logo, IntelliEye, the IntelliEye logo, IntelliMirror, IntelliSense, J/Direct, JScript, LineShare, Liquid Motion, Mapbase, MapManager, MapPoint, MapVision, Microsoft Agent logo, the Microsoft eMbedded Visual Tools logo, the Microsoft Internet Explorer logo, the Microsoft Office Compatible logo, Microsoft Press, the Microsoft Press logo, Microsoft QuickBasic, MS-DOS, MSDN, NetMeeting, NetShow, the Office logo, Outlook, PhotoDraw, PivotChart, PivotTable, PowerPoint, QuickAssembler, QuickShelf, RelayOne, Rushmore, SharePoint, SourceSafe, TipWizard, V-Chat, VideoFlash, Virtual Basic, the Virtual Basic logo, Visual C++, Visual C#, Visual FoxPro, Visual InterDev, Visual J++, Visual SourceSafe, Visual Studio, the Visual Studio logo, Vizact, WebBot, WebPIP, Win32, Win32s, Win64, Windows, the Windows CE logo, the Windows logo, Windows NT, the Windows Start logo, and XENIX, among others, are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or in other countries. 

Sun, Sun Microsystems, the Sun Logo, Ultra, AnswerBook 2, medialib, OpenBoot, Solaris, Java, Java 3D, ShowMe TV, SunForum, SunVTS, SunFDDI, StarOffice, and SunPCi, among others, are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries 

VSFlexGrid Pro is a trademark of ComponentOne LLC,Copyright 2001.All rights reserved. 

J-Integra is a trademark of Intrinsync Software, Inc.

Design Patterns: Elements of Reusable Object-Oriented Software, by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides. Copyright © 1995 by Addison-Wesley Publishing Company, Inc. All rights reserved.

THIRD PARTY CODE, THIRD PARTY LICENSES, AND ACKNOWLEDGEMENTS

Note that in the text below, "Program" refers to Rational® XDE™ software and associated documentation.The Program is composed of multiple separately written and copyrighted modular software components. Some of the components are provided under separate, non-Rational licenses that permit copying, modification and redistribution of those components. Such components are licensed pursuant to the terms of the available license. The components and applicable license terms are set forth below.

I. ComponentOne VSFlexGrid

This product includes VSFlexGrid software developed by ComponentOne LLC. VSFlexGrid Pro is a trademark of ComponentOne LLC,Copyright 2001.All rights reserved.

II. Intrinsync Software J-Integra

This product includes J-Integra software developed by Intrinsync Software Inc. J-Integra is a trademark of Intrinsync Software, Inc.

III. Rhino JavaScript 1.5R1

The Program is accompanied by software developed by Mozilla as part of the Rhino project. The Rhino code included with the Program in XDE\hshell\plugins\com.rational.hshell.ratltool\js.jar or XDE\JavaScriptPkg\js.jar includes modifications necessary to embed the scripting engine with the Program. The source code corresponding to these modifications can be found in the directory "XDE\License Information\Rhino". Your use of Rhino in binary code form accompanying the Program is subject to the terms and conditions of the Netscape Public License Version 1.1 which is found at "XDE\License Information\Rhino\NetscapePublicLicense-1.1.html" and on the Internet at (http://www.mozilla.org/MPL/NPL-1.1.html). Source code for Rhino is available at (http://www.mozilla.org/rhino/) under the terms of the Netscape Public License 1.1.

IV. mpack/munpack

The Program is accompanied by software developed by Carnegie Mellon University. The mpack code included with the Program includes minor modifications. The source code corresponding to these modifications can be found in the directory "XDE\License Information\mpack". Your use of mpack in binary code form accompanying the Program is subject to the terms and conditions of the license that is found at "XDE\License Information\mpack\mpack_license.txt". Specifically, mpack is:

(C) Copyright 1993,1994 by Carnegie Mellon University All Rights Reserved.

Permission to use, copy, modify, distribute, and sell this software
and its documentation for any purpose is hereby granted without fee,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in
supporting documentation, and that the name of Carnegie Mellon
University not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior
permission.  Carnegie Mellon University makes no representations about
the suitability of this software for any purpose.  It is provided "as
is" without express or implied warranty.

CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.

Portions of this software are derived from code written by Bell
Communications Research, Inc. (Bellcore) and by RSA Data Security,
Inc. and bear similar copyrights and disclaimers of warranty.

V. Expat 1.0.2

The Program is accompanied by software developed by James Clark. The Expat code included with the Program includes minor modifications. The modifications can be found in the directory "XDE\License Information\Expat". Your use of Expat in binary code form accompanying the Program is subject to the terms and conditions of the Mozilla Public License 1.0 which is found at "XDE\License Information\Expat\MozillaPublicLicense-1.0.html" and on the Internet at (http://www.mozilla.org/MPL/MPL-1.0.html). Source code for Expat is available from (http://www.jclark.com/xml) under the terms of the Mozilla Public License.

VI. Xerces-J 1.4.4 and Xalan 1.2

The Program is accompanied by software developed by The Apache Software Foundation as part of the Apache XML project. The Xerces code included with the Program in XDE\hshell\plugins\org.apache.xerces\xerces.jar (or XDE\AddIns\common) includes no modifications. Your use of Xerces in binary code form accompanying the Program is subject to the terms and conditions of the Apache Software License 1.1 which is found at "XDE\License Information\Xalan-Xerces\ApacheSoftwareLicense-1.1.txt" and on the Internet at http://xml.apache.org/LICENSE. Specifically, Xerces is:

 * Copyright (c) 1999 The Apache Software Foundation.  All rights 
 * reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer. 
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in
 *    the documentation and/or other materials provided with the
 *    distribution.
 *
 * 3. The end-user documentation included with the redistribution,
 *    if any, must include the following acknowledgment:  
 *       "This product includes software developed by the
 *        Apache Software Foundation (http://www.apache.org/)."
 *    Alternately, this acknowledgment may appear in the software itself,
 *    if and wherever such third-party acknowledgments normally appear.
 *
 * 4. The names "Xerces" and "Apache Software Foundation" must
 *    not be used to endorse or promote products derived from this
 *    software without prior written permission. For written 
 *    permission, please contact apache@apache.org.
 *
 * 5. Products derived from this software may not be called "Apache",
 *    nor may "Apache" appear in their name, without prior written
 *    permission of the Apache Software Foundation.


   THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR
   IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
   WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
   ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
   ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
   LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
   DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
   THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
   OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
   This software consists of voluntary contributions made by many
   individuals on behalf of the Apache Software Foundation. For more
   information on the Apache Software Foundation, please see http://www.apache.org/.

VII. LEAD Technologies LEADTOOLS

Portions of this product were created using LEADTOOLS (c)1991-1999, LEAD Technologies, Inc. ALL RIGHTS RESERVED.

VIII. Regex

This product includes Regex software developed by Dr. John Maddock Copyright (c) 1998-1999.

IX. Summit BasicScript

This product includes BasicScript © 1996-2001, Summit Software Company.

PATENTS

Portions covered by U.S. Patent Nos. 5,193,180 and 5,335,334 and 5,535,329 and 5,574,898 and 5,649,200 and 5,675,802 and 5,754,760 and 5,835,701 and 6,049,666 and 6,126,329 and 6,167,534 and 6,206,584. U.S. Patents Pending. International Patents Pending.

Purify is licensed under Sun Microsystems, Inc., U.S. Patent No. 5,404,499.

GOVERNMENT RIGHTS LEGEND

Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in the applicable Rational Software Corporation license agreement and as provided in DFARS 277.7202-1(a) and 277.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct. 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 227-14, as applicable.

WARRANTY DISCLAIMER

This document and its associated software may be used as stated in the underlying license agreement. Rational Software Corporation expressly disclaims all other warranties, express or implied, with respect to the media and software product and its documentation, including without limitation, the warranties of merchantability or fitness for a particular purpose or arising from a course of dealing, usage, or trade practice.