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

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

The following operating systems are tested and supported: 

• Windows 2000 Professional, Service Pack 2 or Service Pack 3
• Windows 2000 Server, Service Pack 2 or Service Pack 3
• Windows 2000 Advanced Server, Service Pack 2 or Service Pack 3
• Windows XP Professional, Service Pack 1

Notes:

• This release does not support Windows NT.
• For the latest information about operating system support, check the latest version of this document at http://www.rational.net/XDEcenter.

Level 1 support for these languages:

• Dutch
• Hebrew
• Traditional Chinese
• Korean

Level 2 support for these languages:

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

Notes:

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

• Microsoft Visual Studio .NET 2002
• Microsoft Visual Studio .NET 2003

• Internet Explorer 5.5 with Service Packs 1 or 2
• Internet Explorer 6 without any service pack or with SP1
• Netscape 7.0

Configuration Management Software

Supports:

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

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

• For ClearCase v.2002.05.00, patch 15

To verify the latest patch information for your version of ClearCase, go to http://www.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. 

Note: For enhanced model integrity, Rational recommends that you either install the most recent patches for ClearCase 2003.06.00 or disable enhanced ClearCase menus in Visual Studio .NET. For more information, see defect 240709, under "Known Issues."

Category

ID

Description

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

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

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

513643

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

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

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

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

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

The following steps will reproduce the defect:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Preconditions for this defect are as follows:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Workaround: Create a data model and use the command again.

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

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

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

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

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

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

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

Workaround: If you want to use SitePrep.exe directly, it is critical that you configure the shell selection for Rational XDE and Rational PurifyPlus (if installing the Developer Plus Edition) to include only shells known to be present on the target systems that will use the SitePrep area for their install. Do not accept the defaults for the Rational PurifyPlus shell configuration; you must modify the defaults to reflect only shells that are known to be present on the target systems. PurifyPlus shell selection defaults to all supported shells. If you run setup using a SitePrep file that assumes the target machine has all of the shells, and it does not, the problem occurs.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Workaround: None.

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

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

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

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

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

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

The Undo command does not work in the Pattern Explorer.

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

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

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

When you validate the Gang of Four C# Pattern, the Facade Pattern contains one or more broken references.

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

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

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

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

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

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

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

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

For example, consider the following code:

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

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

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

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

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

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

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

Workaround: Use the opposite method/property.

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

Workaround: To get the actual object, use the related method that provided the IRXEReference object -- for example, IRXEGeneralization.getTargetElement() for IRXEGeneralization.getTargetElementReference(). Then, from the actual object, call getModel() to get the referenced model.

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

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

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

Workaround: None.

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

Workaround: None.

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

Workarounds:

• Close and reopen the solution. The class selection will work as expected.
• Run Windows as a member of the Administator group.

Workaround: Download and install the hot fix for Rational XDE Developer Plus, "Rational XDE Developer Plus Patch 1," from http://www.rational.com/support/downloadcenter/upgrades/xde.jsp. Note that this fix can also be applied to Rational PurifyPlus for Windows, Rational Purify for Windows, Rational Quantify for Windows, and Rational PureCoverage for Windows.

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

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

Workaround: For this reason, it is always best to engage trace recording just prior to running your application and to end it immediately afterward.

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

Workaround: Select fewer classes at one time.

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

Workaround: Consider the following options:

• Disable your local firewall.
• Configure your firewall to allow socket connections from the Rational XDE application.
• Configure your local firewall to accept connections on ports between 5001 and 15001.
• Disable other software that may be conflicting with ports between 5001 and 15001.

• The Java Plug-in installation wizard starts and leads you through the installation process. (Internet Explorer)
• You are connected to the Sun Web site to download the Java Plug-in. (Netscape Navigator) 

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

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

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.

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

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

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.

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.0\ToolsOptionsPages

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

Workarounds:

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

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

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

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

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.

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

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

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

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

Workaround: Save the model again. The next time the model is opened it opens in the saved state.

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

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

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

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

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

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

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

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

Workaround: Click OK to check out file.

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.

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.

Category

ID

Description

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.

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

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

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.

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

Workaround: When the Browse for Folder dialog box is displayed, do not press Cancel. Instead, select a folder that is neither in a view location nor in the My Computer root directory and press OK. You will get an error message stating that the project must be in a view. When you press OK to release the message, you exit the loop as well.

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

Workaround: Depending on your ClearCase settings, you may need to manually undo the checkouts on these files through ClearCase itself, rather than through XDE in order to perform a Deliver operation.

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.

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

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

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

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

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

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

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

Workaround: Make the view user-defined by checking the User-defined check box on the General tab in the View editor before attempting to forward engineer the view.

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.

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.

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

Workaround: Go to the Pattern Explorer, copy and paste the pattern into a new project, and then update the multiplicity values as follows: Command: 1, Receiver: 1, ConcreteCommand: 1..*, State: 1

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

Workaround: Go to the Pattern Explorer, copy and paste the pattern into a new project, and then update the multiplicity values as follows: Visitor: 1, ConcreteVisitor: 1..*, ObjectStructure: 1, Element: 1, ConcreteElement: 1..*

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

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.

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.

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

Workaround: Make your namespace changes in the code instead of the model, and then use the Synchronize command.

You cannot customize toolbox using Reset Toolbox.

Workaround: Restart Visual Studio .NET.

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

Workaround: Click the pushpin icon on the title bar of the Model Explorer.

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

Workaround: To change the value of the ImplementationFile property for a particular model element, rename its corresponding file in Solution Explorer, and then reverse engineer the file.

(800) 433-5444
(toll free)

(408) 863-4000
Cupertino, CA

(781) 676-2460
Lexington, MA

+ 31 (0) 20 4546 200
Netherlands

+31 (0) 20-4546-201
Netherlands

+61-2-9419-0111
Australia

+61-2-9419-0123
Australia