Rational® XDE(tm) Release Notes

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.

About this Document

The Rational XDE Release Notes contains important information you will need to install and use Rational XDE - Java Platform 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 electronic versions of the Rational XDE Release Notes. This 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.

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 like not only what you see, but what you can do.

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.

What's New in This Release

Rational XDE v2002 Release 2.1

Fixes for Known Issues

See Issues Fixed in This Release for a list of some of the most important known issues that have been fixed in this release.

Rational XDE v2002 Release 2

Frictionless Design and Development

Unleash the Power of Your Patterns

Data Modeling

Web Publishing and Reporting

Enhanced Internationalization Support

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.

Software Guidelines

Rational XDE Packaging and Features

Packaging Information

Rational XDE v2002 Release 2.1 is available in several packaging options for use with IBM WebSphere technologies:

Either of these packages can run as a standalone Rational XDE product, or they can be fully integrated into your IBM WebSphere Studio Application Developer (WSS AD) integrated development environment. The standalone product runs on IBM WebSphere Studio Workbench, and WSWB is installed automatically when you install this Rational XDE package.

Visual Modeling Features

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.

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:

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 than one person to work on the same controlled units at the same time.

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.

Java, J2EE, and JSP-Based Web Modeling and Round-Trip Engineering Features

Rational XDE Professional v2002 Release 2.1 - Java Platform Edition provides fully integrated Java round-trip engineering capabilities in the default Rational shell. This includes code generation, reverse engineering, and automatic round-trip engineering, all of which are accessible from the shell's Project Navigator, from the Model Explorer, and from diagrams.

As you work in the Rational XDE integrated development environment, you will find that it provides a flexible, feature-rich environment for Java and Web application development:

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:

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.

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.

RUP Configuration for Java Developers

When you purchase Rational XDE v2002 Release 2.1, you also receive RUP Configuration for Java Developers (RCJD).

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.

The RCJD is a role-specific process configuration of the RUP, created to provide a streamlined process for architects and developers who are building enterprise business applications. It consists of the essential developer-focused activities, artifacts, concepts, and guidelines from the base RUP requirements, analysis and design, and implementation disciplines, combined with a RUP plug-in for developing application user interfaces.

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

Getting Help and More Information

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

What Help Is Available?

To access Rational XDE online Help, click Help > Help Contents. If the Help for an information set other than Rational XDE appears, expand the list box in the navigation area (upper left portion of the Help perspective), and select Rational XDE.

To access the complete Rational XDE information set, expand the Contents hierarchy.

To open a Search dialog box that you can use to find any term within the Rational XDE Help information set, click the Search tab at the bottom of the navigation area. Note that the search always applies to the currently active information set. To search for Help topics or terms in any available information set, simply expand the list box in the navigation area, and click the name of the information set you want.

To access links to additional Rational XDE resources, including the Rational Developer Network, XDE Knowledge Center (which includes links to the latest version of the Release Notes), the XDE Tutorial, and other information, make sure that you are in the Modeling perspective, and click Help > Rational XDE Resources. You can also access the Rational XDE Resources topic from within the Rational XDE Help. In the Rational XDE Help Contents, expand the Modeling with Rational XDE Software Help book, and click Rational XDE Resources.

Controlling the Way that Help Is Displayed

As the user, you have significant control over how this Help appears in the Rational XDE environment. You can display Help in any of the following ways:

Note that because a different Help view can be associated with every perspective, you can mix and match these view types for each perspective within the same session, and have a different Help topic open in each perspective, as needed.

In addition to controlling the way Help is displayed, you can ensure that the selected topic in the Help table of contents and the actual Help topic displayed are always synchronized. To do this, click the Table icon to the right of the Help view title bar.

Displaying Help in Its Own Perspective

When you display Help in its own perspective, it completely obscures other active perspectives while it is selected. You may want to display Help this way if you are reading the Help topics to learn about some aspect of Rational XDE. However, if you want quick help on something you are working on, you may want to use one of the other methods of displaying Help.

Displaying Help as an Embedded Help View

When you display Help as an embedded view in another perspective, the view is usually too small to read. However, you can resize the view, drag the view to a new location within the perspective, or quickly (and temporarily) maximize it, to make it more legible.

Displaying Help as an Embedded Thumbtack View

When you display the online Help as an embedded thumbtack view, the Help itself disappears from the screen and is replaced by a question mark icon in the left perspective toolbar. Displaying Help in this way provides fast access to embedded Help without constantly taking up your screen real estate. The fast access view cannot be moved or undocked, but it can be resized, closed, and maximized.

Displaying Help in a Floating Window

When you display Help in a floating window, you can move it out of the way to any location on your desktop. Note that the display options available from the context menu for the Help title bar change when you undock the window, and keep in mind that the Help view disappears when you switch to a different perspective.

Compatibility Issues

Rational XDE Models from Previous Versions

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)

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

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.

Note: If you set the AppliedProfiles property and the Integrated Use Case Management shortcut menus remain unavailable, follow these steps to enable them:

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.

Rational XDE with Rational ClearCase

Setting ClearCase Options

When running Rational XDE with Rational ClearCase, consider the recommendations for setting ClearCase options, described in the following table. To access these options, click Window > Preferences; then, in the Preferences dialog box, select Rational ClearCase and click Advanced Options.

Preserving File Time Stamps During Checkin and Checkout

If you are using ClearCase 4.2 or ClearCase v.2002.05.00, or ClearCase LT v.2001A.04.00 or ClearCase LT v.2002.05.00, checking in or checking out a file that is open in an Application Developer or Workbench editor can cause a warning to appear with a message such as one of the following:

For ClearCase v.2002.05.00 or ClearCase LT v.2002.05.00, you can resolve this issue by activating the options to preserve file timestamps when they are checked in or checked out. ClearCase 4.2 and ClearCase LT v.2001A.04.00 do not have these options, but the latest patches activate the same behavior. See Setting ClearCase Options for information on recommended ClearCase options. See Hardware and Software Requirements for supported software information.

Working with Snapshot Views

Maintaining File History

The way the IBM WebSphere Studio Workbench implements refactoring operations, such as move, rename, and delete, does not take into account the possibility of versioned namespaces (directories). This makes it more difficult to maintain an element's full history when working in an environment, such as Rational ClearCase, that does provide this functionality. In order to maintain history when using refactoring operations on Rational XDE models, and other artifacts such as Java code that are stored in Rational ClearCase, you will need to perform some operations outside the Rational XDE development environment. The steps required to perform these operations are documented in the Rational ClearCase Help, under the Tasks grouping. In this group, you will find detailed information on renaming, moving, and deleting elements. A Perl script is also provided to reduce manual steps and make these operations easier.

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.

Installing and Uninstalling Rational XDE

Installation Issues

Installing Rational XDE

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:

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:

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.

Note: Uninstalling Rational XDE Professional v2002, Java Platform Edition for WSS AD also removes the ClearCase plug-in. When uninstalling Rational XDE for WSS AD, contact Rational Technical Support.

Getting Started with Rational XDE

Starting Rational XDE

Note: If you installed Rational XDE to work with IBM WebSphere Studio Application Developer (WSS AD), Rational XDE is fully integrated into the WSS AD environment. Starting Rational XDE starts WSS AD, and your work can all be done within this integrated development environment (IDE).

Modeling Your Code

Once installation is complete, you can follow these steps to create a new modeling project and familiarize yourself with the many features that Rational XDE provides:

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.

You should note, however, that you cannot use the Getting Started model for generating code. For details on generating code see Modeling Your Code .

If you are not generating code, you can follow these steps to start modeling by creating and opening a new instance of the Getting Started model:

Upgrading and Migrating Models to Rational XDE v2002 Release 2.1

Upgrading Models to Rational XDE v2002 Release 2.1

Rational XDE v2002 Release 2.1 is compatible with models created in earlier versions of Rational XDE. When you open a model that was created in an earlier release, the model and related files go through an automatic model conversion process.

Important: During the model conversion process, you have the opportunity to save a backup copy of your Rational XDE v2002 model before the upgrade takes place. This is highly recommended because, once a model is upgraded to Rational XDE v2002 Release 2.1, opening the model in an earlier version of Rational XDE can cause data loss.

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.

In either case 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, Java models created using Rational Rose J need to go through several steps before you can use them in Rational XDE:

The following Rational XDE Help topics provide more information on migrating Rational Rose models to Rational XDE:

Restrictions and Guidelines

General

Moving and Renaming Model Files

When you create a model and make some of its packages into separate subunits, you must use the Model Explorer to rename or move the subunit files. If you use the Navigator or the file system to do this, the model references to the subunits will be unresolved. Note that the drawing surface will correctly show that the references cannot be resolved, but the Model Explorer will not show the icon that normally indicates unresolved references to model elements. You can confirm this problem by checking your file system for zero length storage units (a size of zero bytes) in a sub-directory under your model's root directory. These zero length files will have the same name as the original storage units.

To fix this problem if you inadvertently rename or move a file outside the Model Explorer, you must undo the move or rename operation; that is, rename the storage unit to its original name in the Navigator, or move the storage unit back to its original location using the Navigator. You must also repair the broken references caused by the update.

If you are uncertain which elements correspond to the subunit, follow these steps to locate the subunit and repair the reference. If you know which elements and subunits should be associated, go directly to step 6.

Important: If you want to rename and relocate subunits in the future, be sure to do so only from the Model Explorer.

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:

For information on cut/copy/paste and drag-and-drop actions specific to Java models, see Cut/Copy/Paste of Java Model Elements, later in this section.

Intra-model Considerations

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:

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.

UML and Java Interfaces

Development Accelerators

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

To import the GoF/Java 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/Java pattern model is write-enabled, 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.

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.

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:

Free Disk Space

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

Configuration Management

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

Comparing and Merging Rational XDE Models Using Rational ClearCase

Compare and Merge

Comparing and Merging Models

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.

Java and Web Modeling

Application Servers

Code-to-Model Synchronization and Code Generation

The automatic compilation setting is enabled by default for XDE Java projects. This setting causes incremental compiles to occur as each code change is written to file, which in turn causes code-to-model synchronization and code generation to perform much slower code generation. To change this setting, click Window > Preferences > Workbench, and select or clear Perform build automatically on resource modification.

When round-trip engineering, follow these guidelines regarding source root settings for your projects and code models:

Cut/Copy/Paste of Java Model Elements

If you do perform these actions, the unique IDs (modelguids) present in the pasted code will be correlated to the original model element and your gesture will not be interpreted to mean "add a new class." You will then begin to see unpredictable results during subsequent round-trip engineering.

Moving nested classes in a Java code model (that is, dragging and dropping, or cutting and pasting) does not result in a corresponding relocation of the source code for those classes. It will instead result in creation of a new class with no body code at the new location, leaving the original class where it was. To complete this action, you must cut the nested class's body code from the original source file and paste it into the new source file, then delete the old nested class element from the model.

For other, general cut/copy/paste guidelines for this release of Rational XDE, see Cut/Copy/Paste Behavior, earlier in this section.

Enterprise Java Bean Diagrams

When you create an Enterprise Java Bean (EJB) in your model, a class diagram entry is created in the Model Explorer. This diagram includes the bean component, classes, and interfaces, which you can drag and drop onto diagrams on the model's drawing surface.

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.

When opening the model, if Rational XDE detects any unresolved cross-model references, correct the references by using the Location Registry dialog box, which appears automatically.

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.
	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.
	76898	Toolbox icons are missing when installing to path, uninstalling, and then re-installing Rational XDE to a different path. Workaround: Reset the toolbox by right-clicking Toolbox > Customize > Reset.
	77069, 84240	If you install more than one edition 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.
	76643	If you are using WSS AD and have installed the WebSphere Application Server with HTTP Services selected, there is a directory under x:\Program Files\IBM and the WebSphere Application Server installation may change it to lower case (x:\Program Files\ibm). If the directory is in lower case, you will need to stop all IBM HTTP Services and DB2 Services then rename the IBM directory to all upper case and restart Windows. This can be done prior to or after installing Rational XDE. If you do not make this change, it will prevent XDE modeling projects from functioning.
	77828	Uninstalling Rational XDE Professional v2002, Java Platform Edition for WSS AD also removes the ClearCase plug-in. When uninstalling Rational XDE for WSS AD, contact Rational Technical Support.
	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.
	88055, 90056	Rational XDE will not launch if non-alpha numeric characters are used in the install path. No warning is given during installation.
	86372	If, for some reason, you need to reinstall Rational XDE v2002 after having installed XDE Rational v2002 Release 2 or Release 2.1, please contact Rational Technical Support for assistance.
	86673	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 should not be seen on future upgrades.
IBM WSS AD Integration	84799	IBM WSS AD users are strongly encouraged to download the latest WSS AD patches, available from IBM at: http://www-3.ibm.com/software/ad/studioappdev/support. These patches address various problems, including several that occur in the WSS AD EJB Editor and EJB Extension Editor when the Update WSS AD from XDE feature is used; they also prevent certain unnecessary messages that otherwise appear when you are browsing code. The patch that fixes the Editor problem is IBM reference JR17012.
	85431	If you use the Update WSS AD from XDE shortcut menu command, you may get an internal error message, if the EJB Extension Editor is open in the J2EE Perspective and the Editor is expanded to show details that should be updated. This problem is caused by a limitation of the EJB Extension Editor. Workaround: Close the Extension Editor and update again from within Rational XDE.
	87381	If you click Help > Feedback while a model is open, you get an error message and you can no longer use Rational XDE. Workaround: Close and reopen Rational XDE.
Internationalization	76416, 80571	If the operating system language is different from the language of the character set you are using to enter text, when project files and storage units are created using extended characters, the extended characters are displayed correctly in diagrams, but not in the Model Explorer. Other display character problems may also occur. Workaround: Ensure that the operating system language and the text entry language are the same.
	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).
	82143	When downloading the Java plug-in required for web publishing and reporting, if you are running a Japanese operating system, 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.
	82080	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 Window > Preferences > Rational XDE > Appearance > General > Default Font, and choose System from the font list.
	84595	The « and >> characters are not supported in Simplified Chinese. Therefore, when you add a shape to the drawing surface, the name in the model explorer is prefixed by two question marks (??). Two question marks are added with each subsequent edit of the name as well.
	84596	When exporting a Rational XDE model as a template on a Japanese operating system, do not include special characters or double-byte characters in template descriptions or names, or the template will not appear in the list of available templates. Note that the file will still be saved in your file system.
	84598	Copying a model in the Navigator window does not work for the following languages: Japanese, Korean and Chinese.
	85402, 85754	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.
	86663	Rational XDE overwrites the localized versions of Rational Suite readme and release notes files with English versions. The Japanese versions are available on the original distribution CD. Workaround: To restore the Japanese versions to your system, copy them from the CD to their original installed locations, or access them directly from the CD.
General XDE	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.
	29312, 55125, 77420	Mnemonic keys (alt<key>) do not work in the Preferences window or in the Find/Replace output window. Workaround: Use Tab and Shift+Tab to navigate to the desired button or field.
	71831, 72139	There are several known issues associated with enabling and disabling specific XDE features such as Java, J2EE, and so on. None of the known issues results in data loss; however, you should generally avoid turning features off and on by using the Addin Manager.
	72662	Rational XDE does not detect files changes that do not originate from within XDE. For example, file changes resulting from the use of an external editor (whether started from within XDE or not) are not automatically detected. However, changes that are made using the internal editors (model changes or changes to Java files using the internal Java editor) will be detected and processed. Workaround: Manually retrieve the latest version of the file.
	73580, 75593	When you use the Tab key to navigate between views or to select items, the selection sometimes appears to become lost or stuck, such that continuing to press the Tab key no longer has an effect. Workaround: In some instances, pressing Shift + Tab unblocks the cursor and allows you to cycle through in reverse. If not, use the mouse pointer to make your selection.
	73589	Cannot use arrow keys to navigate through the properties in Properties view. Workaround: Use the mouse to collapse or expand categories.
	72292	You cannot display the Toolbox's context menu by using the keyboard. Workaround: Right-click in the toolbox to display the context menu.
	75121	When a dialog box is open, attempting to modify your model (for example, adding, removing, or rearranging shapes; changing model documentation, and so forth) may have unpredictable results, or in some instances, may cause abrupt termination of the XDE application. Workaround: Close all dialog boxes before modifying your model.
	75130	When editing properties on a tab in the Properties dialog box, any changes made on the active tab will be committed when you switch to another tab.
	75532	WSWB and WSS AD environments work according to Perspectives. Not all commands are available when a given Perspective is active. For example, when the Help Perspective is active, you cannot access modeling commands. Workaround: Change to the appropriate Perspective.
	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
	76994	When a Microsoft Word document in a project is opened from the Workbench, no scroll bars appear in the document window. Workaround: Use cursor keys and page keys when focus is applied to the document window.
	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.
	79300	Using a context menu (right-click) to close a Rational XDE window yields unpredictable results. Workaround; Use the Close button (X in the right window corner) to close the window.
	80303	In some cases, you must rename a newly created activity graph or state machine, or you must close the model that contains it, before you can delete the activity graph or state machine.
	84590	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.
	84594	Using Rational XDE standalone (WSWB) on Microsoft NT4, undocking a window can cause it to disappear.
	84051	On NT4 systems, when working with a very large project in Rational XDE, upon exit, you may receive the following harmless runtime error, which you can safely ignore: Microsoft Visual C++ Runtime Library Runtime Error! Program:...Program Files\IBM\Application Developer\jre\bin\javaw.exe R6025 -pure virtual function call
	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.
	85599	If you try to open a model files or start a Type Manager session while closing down Rational XDE or the WSS AD IDE, you get an error, and you will not be able to complete the open or start action.
	87203	When you create a model and make some of its packages into separate subunits, you must use the Model Explorer to rename or move the subunit files. If you use the Navigator or the file system to do this, the model references to the subunits will be unresolved. Note that the drawing surface will correctly show that the references cannot be resolved, but the Model Explorer will not show the icon that normally indicates unresolved references to model elements. Workaround: See Moving and Renaming Model Files in the Restrictions and Guidelines section of the Release Notes.
	598662	Do not use Notepad to edit a model file. Notepad sometimes adds non-ascii characters to the first line of the file, causing corruption of the model files. Workaround: Use Wordpad or an XML editor.
Code Templates	77118	When resolving a reference to a target model element, the target model opens, but the Edit Binding dialog box may not appear. Workaround: Click Code Templates > Edit Binding again after the target model is open.
	86074	At code template expansion time, if there are errors, the error line number reported is not always correct.
	86671	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	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.
Compare and Merge	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.
	81867	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	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.
Configuration Management	58250	If you are using ClearCase for configuration management and source control of your Rational XDE projects, all projects in the workspace must be either UCM-based or Non-UCM based. Projects cannot be a combination of both UCM-based and NON-UCM-based.
	72785	When operating in a snapshot view under ClearCase 4.2 with the recommended patch lineup, checking out a file from Rational XDE will result in the current version in view being checked out, which may not necessarily be the latest version, as specified by the view's configuration specification. This situation can occur when multiple users are sharing a development branch through different views. Users would only become aware of this condition when checking in a file because they would be prompted to merge the changes. This situation does not occur when dealing with ClearCase through the Windows or ClearCase Explorers; however, the same problem occurs when using cleartool from the command line.
	72818	Disconnecting from ClearCase while XDE is running will result in a series of errors being displayed in the ClearCase Console upon execution of a ClearCase action. This will also cause some operations to become unavailable. If this happens, it is recommended that you exit and restart Rational XDE in order to get the ClearCase plugin back in disconnected mode. This will ensure that the Hijack menu option is available and that you can continue working. Workaround: To resolve the problem, exit Rational XDE, then restart it again to return to disconnected mode. To prevent the problem, before disconnecting a workstation from the network, exit Rational XDE.
	76766 (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, the WSW or WSS AD shell may lock. Workaround: Click Cancel if a checkin or checkout operation prompts you for a merge, 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 inside the shell. This issue is caused by a ClearCase problem, which is being tracked as CMBU00060282.
	83407	If you are working with ClearCase 4.2 and have more than one view on the same stream, you will not be able to check out the same file from both streams from inside Rational XDE. Specifically, if you check out a file from one view and then check out the same file from the other view, you will encounter an error stating that the file cannot be checked out because it is already checked out, reserved. This will occur even if you select the Unreserved if already reserved option during checkout. Workaround: Perform an unreserved checkout of the file from outside Rational XDE.
	84698	When running Rational XDE on an NT4 system, the ClearCase menu may not be visible. Workaround: Click in the Model Explorer window to reactivate the ClearCase menu.
	85126, 85618 (CMBU00061941)	Attempting to add a nested directory structure that is three levels deep or greater to ClearCase 5.0 may cause the operation to fail and a dialog with the following message to be displayed: Error adding the file [name] to source control. A similar operation of adding a new Enterprise Modeling Project to ClearCase 5.0 all at once will also result in the same failure or a crash. This is a known ClearCase defect and has a defect number of CMBU00061941. For the status of this ClearCase defect, please contact the ClearCase Technical Support group at Rational Customer Service.
	85590	Using IBM VCM configuration management software instead of Rational ClearCase (the default integration provided with Rational XDE) is not recommended, although it is possible for knowledgeable users to do so. Note that, although it is technically feasible to have both configuration management providers active at the same time, it is not recommended because conflicts within the user interface make this mode of operation very complex. Workaround: Use the following procedures to switch between the configuration management systems: To disable ClearCase and enable VCM: Exit Rational XDE, if it is currently running. Go to \RationalXDEinstalldir\hshell\plugins\com.rational.clearcase folder. If plugin.gui.xml.off does not exist, copy plugin.xml to plugin.gui.xml.off. Run the enable_vcm.bat batch file. Copy plugin.nogui.xml.off to plugin.xml. Delete plugin.xml.off. Start Rational XDE. Click Perspective > Reset to reset the views in the perspective. To disable VCM and enable ClearCase: Exit Rational XDE, if it is currently running. Go to \RationalXDEinstalldir\hshell\plugins\com.rational.clearcase folder. Run the enable_clearcase_bat batch file. Copy plugin.gui.xml.off to plugin.xml. Delete plugin.xml.off. Start Rational XDE. Click Perspective > Reset to reset the views in the perspective.
	87013	If there is a conflict between two stereotypes in a merge session, the stereotypes will be removed in the merged model, and you will not be notified. This situation will arise if two users are working on a model unit in parallel and each changes the stereotype of the same model element to different values. The first user to submit the changes to the repository will encounter no problems. However, the second user to submit changes will trigger a merge operation. During this operation, the two stereotypes will be discarded silently. Workaround: Add the stereotype back to the model element.
	87414	When comparing and merging model files from within Rational ClearCase, ClearCase attempts to start the Rational XDE Compare/Merge capability. You may receive the following error if you are missing the registry key that is normally created by the ClearCase installation program:: Missing > extended naming suffix after -extNamingSuffix parameter Workarounds: Have ClearCase create the registry key now, or create it manually yourself. To have ClearCase create the registry key: Click Start > Settings > Control Panel. Double-click the ClearCase icon to display the ClearCase Properties dialog box. On the MVFS tab, delete the contents of the Extended Naming Suffix text box, which activates the Apply button. 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 @@.
	87552	When working with Rational XDE, Rational ClearCase, and IBM WebSphere Studio Application Developer, all Rational XDE-related merges during a deliver operation in UCM, or a checkin operation in base ClearCase, start the XDE Compare/Merge facility, even when there are no conflicts to be resolved. When there are no conflicts to be resolved, such merges should occur automatically and silently. This only affects users delivering or submitting changes to a stream or branch to which other users also deliver, such as users sharing a UCM integration stream. Even then, for any given file, this only occurs when the latest version in the destination is not the version on which the changed file was based (that is, someone has submitted a new version of the file since you checked it out, or since you last rebased). Workaround: Complete the merge session in the usual fashion.
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	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.
	84855	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.
	84932	Data Modeling shortcut menu options do not appear after you apply Data Modeling profile to a Blank File in WSWB. Workaround: After applying the profile to the model, if the shortcut menu options for Data Modeling do not appear, click another object in the Model Explorer (for example, the main diagram or another table that has the complete shortcut menu option), and then click in the diagram again. Alternatively, add the Data Model directly, rather than creating a Rational XDE model and then applying the profile.
	85065	Use the following steps to multi-select tables under a single package: 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) 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.
	84604	Foreign key has a keylist property in the Property browser, which can be updated so that it references the column that you want. Create 3 tables (database not relevant at this point). Draw a relationship between the tables such that 2 tables are parents of the other one. 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. 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.
	85718	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.
	91068	To use data modeling wizards in Rational XDE, you must have MDAC installed on your system. This is normally part of your operating system. However, if your system does not have MDAC, you must download it from http://www.microsoft.com/downloads/search.asp? Enter the Product name as MDAC 2.6 and follow the instructions to download to your system.
Enterprise Java Bean Support	68234	Deleting an EJB that is part of a CMP 2.0 persistent relationship does not delete the appropriate cmr fields on the other EJB involved in the relationship. Workaround: Delete the relationship between the beans before deleting the EJB.
	69616	CMP 1.1 Entity Beans do not have complete finder method entries in the deployment descriptor when deploying to WebLogic 6.1. The deployment descriptor should contain tags for the finder methods that can be completed at deployment time. Workaround: Include these tags manually when editing the deployment descriptors during the deploy operation.
	75787	For WAR Deployment to SunRI, there is no way to specify the contents of the resource-ref (for example, JDBC) and welcome-file-list tags. Workaround: When deploying, choose Edit XML Deployment Descriptors, and add the tags manually.
	76651	During deployment, you may not receive error messages even if some essential wizard fields, such as data source, selected server, selected node, and others, are empty. Workaround: Ensure that all the fields on the second screen of the deployment wizard have valid values, except for those that do not apply to your deployment.
	82129	The validation checks do not confirm that CMP field types are either Java primitive types or are serializable, which is required for CMP fields.
	82625	When transforming Data Model tables to Entity beans, foreign keys are not added to the bean. Workaround: Add the keys manually.
	87295	If you create an EJB in a Java model, transform the EJB to a table in a data model, and then forward engineer the table to DDL, the javaw.exe (part of the Microsoft Java virtual machine) stays active. Workaround: Use the Windows Task Manager to locate and end the javaw.exe task.
	82946	When transforming an EJB to Table, the value of the property EJBNameInJar is used for the table name. Therefore, you must ensure that this property does not have characters that are invalid for a table name.
	83782	When deploying or exporting a deployment descriptor, the descriptor is not generated correctly when two beans share the same implementation class.
	84113	When you use Rational XDE to create a bean with both remote home and local home interfaces, create and finder methods return the same interface, instead of returning the local interface in local-home methods and the remote interface in remote-home methods. Workaround: Correct the method signatures manually.
	84187	After transforming a table to an EJB, the data type of the primary key field may be a Java primitive type, depending on the corresponding type of the table key. However, the Java type should be a wrapper class. Workaround: Manually change the type to a wrapper class (for example, change int to Integer).
	84549	If the Rational XDE AutoSync preference is turned off and you start the WSS AD EJB Editor outside of the XDE application, changes you make and save using the Editor may not appear in the Rational XDE model. Workaround: Leave the AutoSync preference on, or open the code editor from within Rational XDE.
	84726	For an entity bean with one primary key, if you rename the bean, the type expression of the field may be incorrect. Workaround: Manually correct the type expression.
	84757	Items that you create in Rational XDE (for example, EJB References or CMR fields) and then remove by using the WSS AD EJB Editors or by editing the deployment descriptor will not be removed from the Rational XDE model. Workaround: Manually remove the items from the model in Rational XDE.
	84847, 82622	The WebSphere proprietary extensions to the EJB 1.1 specification that support bean relationships and inheritance are not supported by Rational XDE.
	85016	If the Primary Key class is removed, the corresponding getter and setter methods in the implementation class are not removed. Workaround: Remove the methods manually.
	84604	Problems deploying EJB-JAR directly in Web Logic 6.1, Service Pack 2. The deployment to BEA 6.1 can occasionally fail. The log file in Weblogic will show that the bean has been deployed and then immediately undeployed. Workaround: Deploy by using the EAR rather than the EJB-jar option in the Deploy wizard. To do this, select the EAR option and do not select any Web components on the web tier page. The EAR file deployment can also have this problem. The EJB should be available for deployment through the Weblogic console as an alternative workaround.
	87310	On WSS AD, the Transform > Transform to EJB shortcut menu command for a table in a data model does not work correctly if you create the bean at the top level of the model (the ejbModule folder in the project). This is because WSS AD requires that all beans go into a package. Workaround: Put the bean in a package. You can create a default package in advance, if necessary.
Java Application Modeling	63390	If you create a UML interface using the Toolbox or the Add UML menu command, it is not possible to generate code or browse code for it. Workaround: To create an interface in a Java code model, use the Java Interface tool in the Java tab of the Toolbox, or use the Add Java > Interface command on context menus.
	67134	When synchronizing a java class with multiple levels of nested (inner) classes while the Eclipse automatic recompilation feature is enabled, you may receive a java.lang.ArrayIndexOutOfBoundsException from org.eclipse.jdt.internal.core.search.indexing.SourceIndexerRequestor.popTypeName. The message will appear in the output window along with the callstack for the exception. This is caused by a bad interaction with the compilation system. Workaround: Perform a manual rebuild of the project (From the main menu, click Project > Rebuild) to ensure the newly generated files are properly compiled.
	64232	When using Autosync, some Add > Java actions result in a series of corresponding updates being performed in the model, such that you are no longer in Edit mode to rename the newly added model element. Workaround: Press F2 to place the name field of the new model element into Edit mode, and change the default name provided by XDE.
	55462	If you embed comments in a list of method parameters that are all on one source line, and then delete a parameter other than the first or last, the associated comments will not be relocated to the correct place in the line. (Note that such comments are not actual valid Javadoc, and as such are not captured in the model.) Workarounds: Use param comments in the method-level Javadoc instead of in-line comments, or, if you must use in-line, per-parameter comments, place each parameter on its own line in the source code.
	65975	If you are using Java round-trip engineering, and you use the Navigator View to rename a file system folder that corresponds to a Java model package, the corresponding source code package statements and model package elements are not automatically updated. Workaround: Use the model to change package names, which will also update the file system folders in the project.
	68006, 74670, 81602	Dragging-and-dropping or cutting-and-pasting nested classes in a Java code model does not result in a corresponding move of the source code for those classes. Example 1: Move a nested class from one class to another. You will see a new nested class in the target class, and new structural code will be generated for that nested class. Any method body code associated with the original nested class will not be copied to the version within the target class. The original nested class will also re-appear in the original parent class in the model during reverse engineering because of the code that was left behind in the original parent class's source code. Example 2: Move a nested class out of its parent so that it is now non-nested. You will see a new non-nested class in the target package, and new structural code will be generated for that class. Any method body code associated with the original nested class will not be copied to the un-nested version. The original nested class will also re-appear in the original parent class in the model during reverse engineering because of the code that was left behind in the original parent class's source code. Workaround: In some cases this behavior may be what you want; for example, you might be trying to create new classes similar to existing ones, and your intent is to rename the new copies and provide slightly different method logic. In cases where your intent is to actually move the method or nested class from one place to another, the workaround is to do the work in code; that is, cut the code from the original source file and paste it into the target source file, after which the next synchronization operation will reflect the desired changes in the model.
	65734	Non-directed associations should not be used in a Java code model because they provide no basis by which Java round-trip engineering can decide which of the associated classes should contain the attribute representing the association. Use only directed association types in Java code models.
	54005	The UML Subsystem element is not supported in Java code models. Its use will cause errors during round-trip engineering. Workaround: In Java code models, always use the generic Package element.
	27669	Do not attempt to disable or re-enable the Java addin (using Window > Preferences > Rational XDE > Addins > Addin Manager). Java round-trip engineering/code-model synchronization features may not work upon re-enabling the addin.
	59676	Java round-trip engineering may have trouble with the formatting of Javadoc or other comments that are reverse engineered from source that has been maintained in a Unix development environment. Workaround: Bring the source into the Windows 2000 environment and open them in the XDE Java editor. After checking their formatting, save them before you reverse engineer them.
	75227	If you have set method Javadoc preferences to automatically generate Javadoc comments, but have also set your Assisted Modeling preferences so that certain methods are automatically generated for new classes (for example, default constructor, finalizer, getter and setter) the expected Javadoc is not generated for the automatically-generated methods. Note that the same problem applies for attribute-level Javadoc, when you create bean properties with individual change management resulting in automatic generation of attributes.
	74449	This version of XDE will permit you to perform the Add Java > Return Body operation on a method that already has a return statement in its code. This will generally result in an unreachable code compilation error. Workaround: Browse Code on method before using Add Java > Return Body, and verify that the method does not already contain a suitable return statement. Or, simply clean up the code after adding the default return body via the model.
	77777	If the Model Explorer view is closed and you reverse engineer a code file by right-clicking the file in the Navigator view, the Model Explorer view may not open. Nevertheless, the project's code model will open and reverse engineering will occur. Workaround: Open the Model Explorer view manually, by clicking Perspective > Show View > Model Explorer.
	74682	The Assistant dialog box for adding a Bean property does not prevent you from using long, double, or float as the type expression when you specify a constrained property. The resulting generated code for the fireVetoableChange() method will not compile. Workaround: Use the Long, Double, or Float wrapper classes for constrained Bean properties.
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.
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.
	61999	Rational XDE creates message connectors in a sequence diagram using the oblique style. Do not manually change the line style to rectilinear as the layout results are unpredictable
	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.
	77166	Messages seem to gravitate toward the lifeline header, especially in the case of wide lifeline names. Workaround: Start messages lower on the lifeline.
	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.
	84595	The guillemets characters (« ») are not supported in Simplified Chinese. Therefore, when you add a shape to the drawing surface, the name in the model explorer, normally prefixed by «», is instead prefixed by two question marks (??). Two question marks are added with each subsequent edit of the name as well.
Patterns Support	35434	The Composite pattern's operation2 value source is set to User, but should be set to User or Collection. Workaround: Go to the Pattern Explorer, copy and paste the pattern into a new project, and then update the value source for the operation.
	60921	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.
	69950	The Apply Pattern Wizard is non-modal with respect to the drawing surface. Workaround: Do not attempt to modify the model, (for example, by creating new elements on the drawing surface) while in the Apply Pattern Wizard.
	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	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	Deleting a template parameter that has been specified as the default expansion location leaves the model in an incorrect and unexpandable state.
	81714	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	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.
	86708	When a RAS package contains .java files (or any file that participates in a build) and the IDE is configured to auto-compile new or changed files, the import takes a long time (approximately 15 minutes). This is because each new file is unpacked from the RAS package and added to the WSS AD project it is immediately compiled and the project built. Since the first files unpacked are often dependent on the other files (or libraries) that are still to be unpacked, the IDE generates many intermediate errors that are not resolved until all the files are unpacked. The end result is that unpacking a RAS file that should take less than a minute will take close to 20 minutes. Workaround: Turn off auto-compile in WSS AD before doing the import.
	90669	Patterns menus are not updated when you install Rational XDE Professional v2002 Release 2 on a machine where Rational XDE Modeler Edition v2002 Release 2 was previously installed. Workarounds: There are two workarounds for this problem: Restore menu defaults: Click Tools > Patterns > Organize Favorites. Click Restore Defaults to remove any existing entries from the Favorites list and restore the default entries, which include only the GoF pattern entries. Update menu while preserving customizations: Click File > Import, and then select RAS from the list. Enter Rationalinstalldir\XDE\Addins\Patterns\hshell\content\GoF.ras as the location from which to import the file. Specify the destination of the imported file by browsing to the desired project or folder. Click Finish to import the GoF patterns and add them to the Pattern Favorites menu, while leaving previous menu customizations intact.
Printing	57053, 26760, 26931	Rational XDE will not print dashed lines correctly on some printers. This is noticeable for UML dependencies and messages.
RequisitePro Integration	84168	The COMServerAddin enables the Rational XDE integration with Rational RequisitePro, which allows you to perform integrated use case management from within Rational XDE. The COMServerAddin is activated automatically during Rational XDE installation when it detects that Rational RequisitePro is installed on the same system. Do not use the Add-in Manager to activate the COMServerAddin yourself, unless RequisitePro is already installed.
Web Modeling	73182	An HTMLInput is not incorporated into an array if you change its name and type to an existing element array. For example, assume you have 3 elements whose name is MyStuff and whose type is Radio. You then create a fourth element with a different name and type. Later, if you rename the fourth element to MyStuff and change its type to Radio, you would expect that the fourth element will now be incorporated into the existing input array; however, this is not the case.
	78799	References to tag libraries using ./ and ../ combinations are not resolved. Rational XDE only supports tag libraries referred to using an alias found in the web.xml file or a fully qualified file path to the .tld. Other combinations will be brought in as dangling references. This will not cause code loss upon subsequent code generations steps. However, you will not be able to visualize your relationships from a .jsp file to the tag library in your model. Workaround: Change your code to use an alias or fully qualified .tld name.
	83890	When you create an EJBReference between a servlet in a Web model and a bean in an EJB model, and then synchronize the servlet model with the code, you may occasionally receive the following error message: *Error: Skipping AssociationEnd ... originated from Class servlet-name* - Cannot resolve supplier Workaround: In the Navigator, right-click the servlet model's project and select Properties. Click Project References,** and check the EJB project option.
	84433	When you import a web.xml deployment descriptor, the context-params tags are ignored.
	85060	Deleted tagclass is not removed from a model during reverse engineering. If you blank out the tagclass attribute in a .tld file and reverse engineer it into a tag library model, Rational XDE will not remove this tag value from the model. Subsequent code generation steps will re-introduce previous tag class back into the code. Workaround: After reverse engineering a .tld file with a newly blanked-out tag-class, manually delete this tag value from the model.
	85354	Tag Library models outside current projects are lost during subsequent reverse engineering. Linking to tag library models located outside of the project that contains the referring .jsp file is not supported. If you draw JSPUseTaglib dependencies to tag library models that are outside of your current project, subsequent reverse engineering steps will remove these dependencies from the model and replace them with dangling relationships. This will not cause code loss upon subsequent code generations steps. Workaround: Move your .tld file into the current project (preferably under webApplication\WEB-INF) and reverse engineer it into the current project. You can then refer to these correctly from Server Pages within the same project.
	85870	Dropping a form onto a diagram and specifying an owner and receiver creates new classes on the diagram, rather than finding classes that already exist. Note that new classes are only added to the diagram, not to the model. Workaround: Delete these classes (and their duplicates from the diagram) and re-add them from the model explorer. The appropriate relationships will then appear.
Web Publishing and Reporting	71502, 79902, 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: Locate the .java.policy file in your home directory. Create the file, if it does not exist. Append the following section to the end of the file: grant codeBase "file:/-" { permission java.io.FilePermission "«ALL FILES»", "read"; }; Save the file. 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.
	82973, 86134	If you click Help in the Publish Model or Generate Model Report dialog box, and then press ESC to close the Help window, the focus moves to the Publish button, but the selection cursor, which you move with TAB, stays on the Help button. It may appear that pressing Enter invoke Help again, when in fact it starts the publishing process.
	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.
	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.
	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.
	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.

Issues Fixed in this Release

Contacting Rational Technical Support

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

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

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

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

This product is accompanied by software developed by the Eclipse Project (http://www.eclipse.org).

II. Sun J2EE Patterns Catalog

The Sun J2EE Patterns Catalog from Sun's Java Center(sm) consulting organization is included in its entirety within this product. The Sun J2EE Patterns are used with permission from the book "Core J2EE Patterns" by Deepak Alur, John Crupi, and Danny Malks, published by Sun Microsystems Press/Prentice Hall. Copyright 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303. All rights reserved. SUN PROVIDES EACH J2EE PATTERN "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

III. ComponentOne VSFlexGrid

IV. Intrinsync Software J-Integra

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

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

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

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

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

IX. LEAD Technologies LEADTOOLS

X. Regex

XI. Summit BasicScript

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.

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.

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

Operating Systems	The following operating systems are tested and supported: Windows 2000 Professional, Service Pack 2 or Service Pack 3 (Service Pack 2 is recommended) Windows XP Professional Windows NT 4.0 Workstation Service Pack 6a. In addition, both Microsoft Windows 2000 Server and Windows 2000 Advanced Server are available as install platforms, although they remain unsupported as primary platforms for Rational XDE. See Installation Issues for more information regarding supported and 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
Supported Platforms	Runs standalone, using IBM WebSphere Studio Workbench (WSWB) technology (WSWB must not be preinstalled) Integrated with IBM WebSphere Studio Application Developer (WSS AD) version 4.0.3 (WSS AD must be preinstalled) Integrated with IBM WebSphere Application Developer, Integration Edition, V4.1.1 (WSAD IE) Note: WSS AD users are strongly encouraged to download the latest WSS AD patches, available from IBM. It is especially important that you download IBM Patch JR17027 from http://www14.software.ibm.com/webapp/download/product.jsp?s=p&pf=&type=s&postsb=&id=SPAT-524G3S. The latest patches address various problems, including several that occur in the WSS AD EJB Editor and EJB Extension Editor when the Update WSS AD from XDE feature is used; they also prevent certain unnecessary messages that otherwise appear when you are browsing code. See Installation Issues for information regarding other versions of WSS AD.
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.
EJB and Web Modeling and Deployment	One of the following platforms and their libraries: WebLogic 5.1 WebLogic 6.1 WebSphere 4.0 Sun J2EE Reference Implementation 1.3 Web Server (Apache) 1.3
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 Software	Supports ClearCase 4.2, ClearCase v.2002.05.00, ClearCase LT v.2001A.04.00, ClearCase LT v.2002.05.00 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 8 and 9 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.

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 this option to make it easy to locate an earlier file version, which can be helpful in recovery from user error. This option is recommended.

Rational XDE Modeling Project	WSS AD Project	Description	Models Added to Project
Simple/Basic Modeling Project	Simple Project	Generic project that contains files and folders.	Blank Model
Java Modeling Project	Java Project	Contain Java code; can be exported as JAR files or into a directory structure	Java Code Model
Web Modeling Project	Web Project	Contain resources for Web applications, including servlets, JSP files, Java files, static documents (for example HTML pages or images), and associated metadata. Deployed as a Web module (WAR file).	Java Code Model, Virtual Directory Model, JSP Tag Library Model
Enterprise Application Modeling Project	Enterprise Project	Contain a combination of Web modules, EJB modules, JAR files, and application client modules. Deployed as an enterprise application (EAR file).	None
EJB Modeling Project	EJB Project	Contain metadata files (such as deployment descriptor, IBM extensions, RDB mappings) for the EJB application; also contains Java source files, stubs and compiled code for enterprise beans. Deployed as an EJB module (JAR file).	Java Code Model
Application Client Modeling Project	Application Client Project	Contain resources for application client modules that run on networked client systems or for applets that run in a browser; deployed as a JAR file.	None

Category	ID	Description
Installation	89092	This release corrects the condition that prevented publishing of diagrams that contained grouped objects. All requested diagrams are now published, with no limitation caused by grouped objects.
IBM WSS AD Integration	85577	In a few circumstances, EJB security roles or method permissions defined in the EJB Editor (Security pane) are lost by Rational XDE: Define a security role, but don't define any method permissions that use it. Workaround: Define at least one method permission for each security role. Define a method permission for a method that is inherited from an EJB standard interface or class, but which is not overridden by the bean. For example, you want to define a method permission for the remote interface method "getEJBHome()". XDE can only remember permissions for methods that are explicitly declared in the bean's interfaces. Workaround: Declare the inherited method in the interface BEFORE defining the method permission for it in the EJB Editor. There is also one situation in which a deleted security role may be reactivated by Rational XDE: Define a method permission for the (now-obsolete) role. Save the changes, thereby causing Rational XDE to incorporate the new permission Delete the role in the EJB Editor. Update WSS AD from Rational XDE The old role reappears in the EJB Editor. Workaround: In the Model Explorer, locate the method(s) in which the old method permissions were defined for the obsolete security role. For each method, find the EJBMethodPermission property in the Property Browser. Delete the part of the string that lists the old role.
Internationalization	81214	When you add any element to a model, the element is added to the Model Explorer, preceded by guillemets characters («»). The guillemets characters are not supported in Simplified Chinese and cause numerous problems, such as interpreting the guillemets as question marks (??) and failing to increment the default names of subsequent elements (element1, element2, etc.) Workaround: Click Window > Preferences > Rational XDE > Model Explorer, and set Stereotype to None so that the stereotype does not appear in the Model Explorer. See also 84595.
General XDE
	72003, 67501	You should close windows by clicking the Close (X) button in the upper right corner of the window, rather than by clicking the Close command on the menu; otherwise, you will not be able to re-open the window again during the same session. Workaround: Restart Rational XDE.
	79687, 84588	If you attempt to open an extremely large file from within the Navigator window, Rational XDE may shut down without warning.
	84278, 85848	The Location Registry modeling preference, 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.
Data Modeling	85574	Domain in not a supported data modeling stereotype in the Pattern Asset dialog box.
Enterprise Java Bean Support	87302	The Transform > Transform to EJB shortcut menu command for a table in a data model does nothing if the target EJB Model is set for EJB 1.1 (J2EE 1.2). Workaround: Follow these steps to workaround this problem: Before using the Transform command, click Window > Preferences > Rational XDE > Java > EJB/Servlet Preferences. Set the Default J2EE Version, to 1.3 (EJB 2.0, Servlet 2.3). During the Transform operation, select CMP 1.1 in order to get an EJB 1.1 compliant bean. After comleting all Transform operations, select each new Entity bean and change the EJBVersion to 1.1 in the Property Browser. Change the Default J2EE Version in the Preferences back to 1.2 (EJB 1.1, Servlet 2.2).
Patterns Support	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.
Web Publishing and Reporting	88952	With this release, diagrams are now published exactly as they appear in XDE. Elements that you delete from the diagram in XDE no longer appear in the published diagram, so that there is no longer any unwanted detail.
Web Publishing and Reporting	89092	This release corrects the condition that prevented publishing of diagrams that contained grouped objects. All requested diagrams are now published, with no limitation caused by grouped objects.
Shapes	53896	You cannot easily select multiple nested shapes. Workaround: 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.
	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.
	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.

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

Rational® XDETM - Java Platform and Workbench Edition

Release Notes

Copyright

Fixes for Known Issues

Frictionless Design and Development

Unleash the Power of Your Patterns

Data Modeling

Web Publishing and Reporting

Enhanced Internationalization Support

What Help Is Available?

Controlling the Way that Help Is Displayed

Displaying Help in Its Own Perspective

Displaying Help as an Embedded Help View

Displaying Help as an Embedded Thumbtack View

Displaying Help in a Floating Window

Preserving File Time Stamps During Checkin and Checkout

Working with Snapshot Views

Maintaining File History

Java Plug-in

Free Disk Space

TRADEMARKS

THIRD PARTY CODE, THIRD PARTY LICENSES, AND ACKNOWLEDGEMENTS

I. Eclipse

II. Sun J2EE Patterns Catalog

III. ComponentOne VSFlexGrid

IV. Intrinsync Software J-Integra

V. Rhino JavaScript 1.5R1

VI. Expat 1.0.2

VII. Xerces-J 1.4.4 and Xalan 1.2

VIII. mpack/munpack

IX. LEAD Technologies LEADTOOLS

X. Regex

XI. Summit BasicScript

PATENTS

GOVERNMENT RIGHTS LEGEND

WARRANTY DISCLAIMER

Rational^® XDE^TM - Java Platform and Workbench Edition