11/30/2004
GI11-4685-04
Copyright © IBM Corporation 2002, 2004. All Rights Reserved.
Any reproduction or distribution of this work is expressly prohibited without the prior written consent of IBM Corporation.
This document contains release notes for the Microsoft .NET editions of the IBM Rational® XDE™ Version 2003.06.14 Service Release. Because service releases are accumulative, this document also includes information about the previous service releases, versions 2003.06.01, 2003.06.12, and 2003.13. Where appropriate, material is designated as specific to a particular service release.
This release note document supplements the release notes provided with Rational XDE Version 2003.06.00, so please refer to that document or see the release notes for new product installations of version 2003.06.13, available from the IBM Publications Center (see the note below).
Note: This document was accurate at the time this product was prepared for release. The most recent version of this file is available in the IBM Publications Center at www.ibm.com/shop/publications/order. (To search for the IBM Publications Center, go to www.ibm.com and enter "IBM Publications Center" in the Search field.)
- Search for "GI11-4685-04" to find the latest version of this document in the IBM Publications Center.
- Search for "GI11-4683-04" to find the latest version of the release notes for new product installations of Rational XDE Version 2003.06.13.
Some information is specific to a product package, and is designated accordingly.
Additional updates may be available for this service release. To determine if there is an update that applies to this release, take the following steps:
The capabilities available to you in this service release depend on your packaging option. To determine the package you have installed, see Identifying the Package and Product Build ID below. For more information, see "IBM Rational Modeling Packages" in the Rational XDE Help.
This service release provides the following major enhancements for the .NET platform editions:
This service release provides the following major enhancements for the .NET platform editions:
Note: IBM Rational v2003.06.13 products do not officially support Windows XP Professional, SP2, and the information in this document is based on testing done with a Windows XP SP2 release candidate. The production release of Windows XP SP2 was not available for final testing at the time this document was finalized. Contact IBM Rational Software Support to obtain the latest information on Windows XP SP2 support.
The earlier Rational XDE 2003.06.12 service release provided the following major enhancements for the .NET platform editions:
For .NET Developer and Developer Plus Editions Only
The earlier Rational XDE version 2003.06.01 Service Release provided improved performance and usability, including the following:
This release has no additional hardware requirements beyond Rational XDE Version 2003.06.00.
Note: Upgrading a desktop system or a release area does require a substantial amount of temporary disk space. For more information, see Applying this Service Release to a Desktop System and Applying this Service Release to a Release Area.
This service release includes full support for Microsoft Windows XP Professional, Service Pack 2, and clarified support for Windows 2000 service packs. Previously, the Rational XDE Version 2003.06.13 Service Release included expanded Windows XP Professional support. The Rational XDE Version 2003.06.12 Service Release included new support for Windows NT 4 and expanded database support. It also recommended upgrading to Sun Java Runtime Environment (JRE) plug-in version 1.4.1. The earlier Rational XDE Version 2003.06.01 Service Release added support for Windows 2000 SP4. There are no other changes in software requirements beyond Rational XDE Version 2003.06.00.
| Supported Operating Systems | The following operating systems are tested and supported:
Notes:
|
| Databases Supported | Rational XDE supports data modeling for the ANSI SQL 92 standard and the following database management systems (DBMS):
|
| Web Publishing and Reporting | Web publishing requires the Java Plug-in, version 1.3.1 or later, downloadable from the Sun Web site at http://java.sun.com/products/. Publishing a model to a folder that has double-byte characters in the name requires that you use version 1.4.1_01. |
| Rational Unified Process and Extended Help | The Rational Unified Process, or RUP, and RUP's Extended Help, requires the Sun Java Runtime Environment (JRE) plug-in, version 1.4.1, available from http://java.sun.com/products/archive/j2se/1.4.1/index.html. |
To determine the package and build ID of Rational XDE that you currently have installed, run the Rational Software Installed Product Information utility by clicking Start > Programs > Rational Software > Rational Software Installed Product Information.
Rational XDE does not need to be upgraded if the build ID is listed as 2003.06.14 or later.
This service release can be applied to the following editions of Rational XDE version 2003.06.00, 2003.06.01, 2003.06.12, and 2003.06.13:
Do not apply this service release to any evaluation versions of Rational XDE.
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.
You have two choices at this point. IBM Rational recommends that you choose to upgrade any 2003.06.12 or earlier Rational products to the 2003.06.13 version, then upgrade to 2003.06.14. The other option offered is to uninstall the 2003.06.12 or earlier Rational products, upgrade XDE to 2003.06.14, and then reinstall the 2003.06.12 or earlier Rational products. IBM Rational recommends that you maintain like versions of Rational products, upgrading all products to version 2003.06.13 before upgrading to version 2003.06.14.
If the original Rational product was installed from a CD image (directly
to a desktop or client server), the upgrade must also be done using a CD. If
the original Rational product was installed using a release area, the upgrade
must be done using a newly designated release area. If the original Rational
product was installed using a product download, the upgrade must also be done
using a product download.
If you are unsure of the source of the original installation, the location
of the installation source can be found from the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Product
GUID}
The String Value named “InstallSource” contains the location of
the root directory used for the installation. In the case of a CD installation,
the CDROM drive will be listed. For example, with the CDROM drive mapped to
drive letter E, the InstallSource String Value will contain “E:\Setup\”.
In the case of an installation from a download or a release area created through
the “Enterprise Deployment” install option, the value will contain
the full path to the release area or the location from where the download was
extracted.
The only way to differentiate between an extracted download and a release area
is through the presence of Cabinet files (extension of .cab), found in the
extracted download directory. If the location listed in the InstallSource String
Value contains one or more files with a .cab extension, then the source was
either an extracted download, or CD content copied to the hard disk.
For more information, see defect 454398, under Installing and Upgrading.
You can apply IBM Rational service release version 2003.06.14 to a desktop system only if version 2003.06.13 is already installed on that system.
After you download the file by saving it to your hard disk, double-click the service release patch file to upgrade your IBM Rational products.
Attention: It may take several minutes before the patch installation process displays an indication of activity.
Upgrading a Desktop Using a Patched Release Area
Use this method to upgrade a desktop system that was originally installed from a release area.
Note: The upgraded release area may also be used to install IBM Rational products onto a new system (no existing IBM Rational products installed) or installing additional IBM Rational products onto a system.
Approximately 750 MB of temporary free space is required. The temporary space
is located on the drive associated with the locations listed in the following
two environment variables:
%TEMP%
%SystemRoot%
Upgrading a Desktop by Directly Applying the Service Release File
Use this method to upgrade a desktop system that was originally installed from source media (a CD-ROM or download file rather than a release area). For each IBM Rational product being upgraded, a minimum of 1.5 GB of temporary free space is required.
You may be able to free up temporary space on a drive associated with the locations
listed in the following two environment variables:
%TEMP%
%SystemRoot%
You can apply IBM Rational service release v2003.06.14 to an existing release area only if version 2003.06.13 is already installed in that release area.
Administrators: Apply this service release to a version 2003.06.13 release
area using this command:
msiexec /p {1_drive}:\{1_path}\{msp}
/a {2_drive}:\{2_path}\{msi}
/lv* {3_drive}:\{3_path}\{log}
Where:
/p {1_drive}:\{1_path}\{msp}
specifies the location of the patch file being applied.
/a {2_drive}:\{2_path}\{msi}
specifies the location of the release area and the .msi file to which the service
release will be applied.
/lv* {3_drive}:\{3_path}\{log}
specifies the location of the log file.
Installation of the service release may take a while.
Attention:
This service release upgrades all installed version 2003.06.00, 2003.06.01, 2003.06.12, and 2003.06.13 Rational software products (this is not selectable). It will upgrade Rational XDE only if you have version 2003.06.00 or later. The installer will automatically detect your Rational XDE installation and configure itself accordingly.
To install the service release:
You can confirm successful application of this service release by checking the build ID displayed in the Rational Software Installed Product Information dialog box. For more information, see Identifying the Package and Product Build ID.
You cannot uninstall just the service release from your system. To roll back your system to a version of Rational XDE without the service release, uninstall Rational XDE, then reinstall Rational XDE.
Note: If you do choose to revert to an ealier version of Rational XDE, see defect 137334 in "Known Issues," below.
If you previously installed the XDE Floating License Enablement Kit, please ignore this section. License enablement of your XDE products is unaffected by this service release.
This service release enables you to manage v2003 IBM Rational XDE product's use of floating license keys.
To enable XDE license enforcement:
After you configure XDE to use license keys:
When license enforcement has been activated, XDE behaves as follows:
A valid XDE license key is required throughout the duration of any XDE session, which is initiated when a model is opened and terminated when all models are closed. When the session begins, an attempt is made to check out a license key from the license server. If a license is available, XDE checks out the key for the duration of your session. If no XDE license keys are available on the server, a warning message appears informing you that you do not have a valid key. XDE will continue to operate, and you will continue to see this message while using XDE until a valid license key is acquired.
For information about accessing the online Help provided with Rational XDE, please see "Getting Started" in the Rational XDE Version 2003.06.13 Release Notes for new product installations. For download instructions, see the Scope section above.
When using this product on Microsoft Windows XP Professional, Service Pack 2, you may receive warnings when using online Help. The HTML-based Help files contain active content that is on the hard-disk of the local machine.
Because the Rational Developer Network is now IBM developerWorks Rational, the links to the Rational Developer Network from the Rational XDE Help system may not work properly. If you are not redirected to the correct page, please go to http://www.ibm.com/developerworks/rational/ and navigate or search from there.
The following information is not included in the documentation for Data Modeling in Rational XDE:
Comparing and Pairing Data
The Compare and Sync Wizard has been enhanced to include a Choose Schema dialog box a new Compare dialog box in place of the Select Synchronization Options dialog box. The Compare dialog box lets you scroll through all the database items you want to compare and synchronize, it also includes expand and collapse buttons on the toolbar to help you review your data items in outline form.
Each data item, such as tables or columns, is shaded in a color to help you differentiate the beginning and the ending of all the properties and tagged values of that item.
Differences are identified by a red font accompanied by a red triangle. The toolbar includes the import, export, delete, and ignore buttons, so you can set actions for data items with a difference.
One of the new features added to the wizard is pairing. Pairing lets you align or map data elements that are the same element in the data model and the database or DDL, but are named differently. Pairing will save the tagged values of the data element. Pairing is controlled by a Pair button on the toolbar.To pair data elements:
- Click a data item.
- Click the Pair button.
- Click the matching data item.
You can also separate paired data items by clicking the Unpair button.
After you assign actions to each data item with a difference and pair the data items you want to pair, you can click Next to continue in the wizard.
The following information is not included in the documentation for Modeling in Rational XDE (defect 247772).
Call Event Parameters Now Appear in the Diagram Window
Parameters of an unqualified event are surrounded by a double backslash (\\), similar to messages. When you edit parameters inline using the diagram window, the parameters are created or changed for the specific event. However, on a qualified event (one with an operation), operation parameters appear. When you edit the operation parameters, the changes are ignored and are not reflected in the diagram window, regardless of whether the event has additional parameters or not.
The following information is not included in the documentation for Round-Trip Engineering in Visual Studio .NET editions of Rational XDE (defect 249279).
Exporting a .NET Code Model As a Reference Model
When working with a Visual C# .NET or VB.NET code model, you can choose to export the model as a reference model. By using the Export as Reference Model command on the Round-Trip Engineering toolbar, in the context of the Model Explorer, you make a copy of the code model, modify its properties to transform it to a reference model, and then save it in the same folder as the assembly built from the project.
This export operation can be used to create a reference model when sharing components. For example, you might provide components to other people at the end of an iteration of development. As part of the documentation, you might provide the code model associated with the project that built the assembly. When another user references this assembly from a development project and synchronizes, a reference model associated with this assembly will created by the XDE Round-Trip Engineering (RTE) engine instead of using the supplied code model. This is intentional. In the Visual Studio .NET Edition of XDE, the code model and reference model are two different entities and one cannot be used in place of the other. Currently, there is no interopability between these two kinds of models. In order to help the process of "releasing" a code model along with the assembly built from that project, use this Export as Reference Model command.
If you want to include the code model of a project along with the assembly built from that project, you should export this code model as a reference model and then bundle that along with the assembly. This way, when another user references your assembly directly, the RTE engine will automatically detect the reference model colocated with the assembly. Note
that more than one reference model may be generated, depending on how many other code models, if any, your code model references directly or indirectly. You should include all the generated models along with the assembly.When using this command, consider the following information:
- This command is available only from the Model Explorer.
- This command is visible only if at least one of the selected models in the Model Explorer is a code model. (All selected items should be models.)
- At present, this command is supported only for C# .NET and VB.NET code models.
- The name of the generated reference model is the same as that of the assembly, and the name of the model file will match.
- If the code model being exported is organized into storage units or sub-units, this command will copy them as well. However, when including the model with the assembly, you should make sure you have copied all the sub-units as well. The sub-units are typically in a folder with the same name as the model.)
- This command recursively follows the model references to make sure that all the code models referenced by this code model are also exported, and the dependencies fixed up to point to the newly generated reference models. Even if you are exporting only a single code model, the process may take a long time if it depends on a lot of other code models.
- If there happen to be reference models in the closure of the exported model, those will be left intact. In the case of the standard .NET reference models that are shipped with XDE, these will resolve correctly. However, if there are nonstandard reference models in the closure, then at the end of the export process you should check the generated models for unresolved references. If there are unresolved references, you will see an error message when opening the model. At this point, you can browse to the right model and correct the broken reference.
- This command cannot be reversed. As a consequence, at the end of this command, you will not have the option to undo the operation.
- This command does not have any side-effect on the rest of the system other than the fact that one or more model files are generated on the file system.
This command will end with an error if any one of the following is true:
- The model or one of its subunits is dirty.
- The fix is to save the model.
- The assembly for the project could not be located. The assembly location and name are determined from the project settings.
- The fix is to build the project or solution.
- Any one of the models could not be copied.
- The fix is to make sure you have enough disk space and sufficient permissions.
- The operation failed to set the properties in the model that makes it a reference model. Normally, this will happen only in cases where you have any one of the previously generated reference models open in the Model Explorer. However, if this does happen when that is not the case, try the second workaround below. If it happens consistently (and it is not due to the open reference model), please contact IBM Rational Software Support.
- The first workaround is to close all the reference models generated in a previous run of this command, if you had explicitly opened them.
- The second workaround is to restart the VS.NET session.
The following information is not included in the documentation for Round-Trip Engineering in Visual Studio .NET editions of Rational XDE.
Initial File Settings for C# and Visual Basic
When you add C# and Visual Basic model elements to a nested namespace and then generate code, initial code source files are generated in the project's root directory by default. You can set code-generation options for C# and Visual Basic so that initial files are created in a folder structure that parallels the namespace nesting structure.
To define the location of initial files during code generation:
- Open the Options dialog box, expand Round-Trip Engineering, and then click Code Generation Settings.
- Select the Create directories for nested namespaces check box
- Click OK.
Data modeling database connections need to be updated for Rational XDE version 2003.06.13 or later. For detailed information about the correct setup steps and connection parameters, see the following technotes on the IBM Support and downloads Web site:
Also see the Data Modeler defects listed under Known Issues.
In the earlier service release, you can only open petal model files created using versions of Rational Rose up to version 8.0. In order to import petal model files created using Rose version 8.1 in this service release, use the Save As functionality in Rose to save the version 8.1 petal model file as Rose version 8.0. Once the petal model file is saved to a previous version of Rose, the file can then be opened with this release of XDE. (This is not an issue in Rational XDE 2003.06.12 Service Release.)
The following tables describe the known issues in this and previous service releases.
| Category |
ID |
Description |
| Data Modeler | 139953 |
When using .NET version of Rational XDE, unable to connect to IBM DB2 zSeries data model. Workaround: Install DB2 Connect Personal Edition version 8.1 (or later) on your system. |
140415 |
Users upgrading from Rational XDE 2003.06.12 to 2003.06.13 or later should be aware that the ODBC driver is no longer supported for connecting to a database. Workaround: Instead, for most database systems, the JDBC Thin driver or ADO.NET should be used to connect. For more information, see Restrictions and Guidelines on Using this Release, Data Modeling. |
|
140416,
140865 |
As of Rational XDE 2003.06.13, the details for connecting to IBM DB2 and Oracle databases have changed. In addition, the list of supported drivers has changed. In some cases, the following error message is displayed during a test connection: "Unable to connect to the database with the specified information. Please verify the connection information." Workaround: For more information, see Restrictions and Guidelines on Using this Release, Data Modeling. |
|
728904 |
Certain versions of the client connection tools (DB2 UDB Personal Edition or DB2 Connect Personal Edition 8.1) may stop working with the DB2 UDB database system. This may cause the reverse-engineering process to freeze when going from the database to the data model in XDE. Workaround: First, generate the DDL script from the database, and then reverse engineer from the DDL script to the data model. |
|
| Documentation | Update online Help to include details about the Export as Reference Model command, for exporting .NET code models to reference models. See above, under Product Documentation, Round-Trip Engineering. | |
| Installing and Uninstalling | 460902/APAR IC42702 |
Installing Rational XDE - .NET Edition on a machine running Microsoft Windows XP, Service Pack 1, can result in slow performance for Visual Studio .NET., not only for Rational XDE projects but also C#, Visual Basic, and other projects. Workaround: Upgrade to Windows XP SP1a. If Windows XP SP1 is required, then reducing the hardware acceleration on the Display Control Panel's Advanced Settings panel will alleviate the problem. |
| Category |
ID |
Description |
| Documentation | Update online Help to address editing of event parameters in diagram window. See above, under Product Documentation, Modeling. | |
459662 |
The online Help for freezing a model incorrectly states an expected setting. In steps 3 and 4 of the "Freezing Include Models" topic, you are told to look for the text unitPolicy ="1". Instead, you will normally see unitPolicy="0" when opening a .mdx file. |
|
| Installing and Uninstalling | When upgrading from Rational XDE Version 2003.06.12 to 2003.06.13, code template CLR callouts do not operate. Workaround: Following an upgrade, CalloutCLRManager.dll must be reregistered manually using the regasm.exe utility. To register using the command line:
|
|
| Round-Trip Engineering | When working in a team development environment, unsynchronized items can result if one user accesses a solution using Rational XDE Version 2003.06.12, and a second user accesses the solution using version 2003.06.13 of XDE. The synchronization problem can happen if the version 2003.06.12 user fails to synchronize the solution before closing the solution, and the second user opens the solution from the 2003.06.13 version of XDE to work on the same model elements. Workaround: Use one of the following workarounds:
|
|
| Web Publishing and Reporting | 374617,
458596 |
When you publish a model, upon first opening the model you may see the following error message, "Page cannot be displayed." Workaround: The Web publishing facility cannot access the contents of a model unless the Model Explorer in XDE can access them. For example, constraints that are not visible in the Model Explorer will not be published. The filter settings for the Model Explorer determine what is visible. To modify filter settings for the Model Explorer:
|
|
Category |
ID |
Description |
|||||||||||||||||||||||||
| Configuration Management | 243561 |
If you rename a model element or add a diagram to a saved and checked-in model, the dialog box that appears has buttons only for Checkout, Edit, and Help. The dialog box does not have a Cancel button. If you click the Checkout button, and then click the Cancel button in the next dialog box, the in-memory changes are kept rather than being rolled back. Workaround: If you want to add a diagram to a saved and checked-in model, you need to explicitly check out the storage unit of the diagram. The checkout must be done before making any changes to the model. If you did not check out the model, you can recover by closing the model without saving the changes. |
|||||||||||||||||||||||||
Rational XDE customers who have installed recent ClearCase v2002.05.00 Windows patches (for example, patch 24 and 26) will start receiving prompts to reinstall the XDE/ClearCase Type Manager Installer. This is due to the ClearCase patch overwriting the XDE bindings in ClearCase control files that steer compare and merge operations to the XDE compare/merge facility. Workaround: Uninstall and then perform a reinstall of the XDE/ClearCase Type Manager Installer on the server and on the client. This will have to be repeated after every ClearCase patch install. Monitor future ClearCase patches for fixes for this issue. |
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
| Documentation | 243667,
461206/APAR IC42781 |
The
RXE API documentation does not reflect the inheritance model used in the
Patterns and Code Templates portion of the API. The actual inheritance
used is as follows (indentation indicates inheritance.)
|
|||||||||||||||||||||||||
245889/APAR
IC39101
|
See the description for defect 245889 above, in the "Data Modeler" section of this table. | ||||||||||||||||||||||||||
| Installing and Uninstalling | 137334
|
If you are reverting from Rational XDE version 2003.06.12 to an earlier version of XDE, such as version 2003.06.00, you may see error messages during synchronization. See defect 137334 below for a complete description. | |||||||||||||||||||||||||
| 454398 | When
upgrading from a previous 2003 version of an IBM Rational product using
the 2003.06.12 CDs, the following message may continue to display with
Disk 1 in the CD drive: “Please insert the disk: Disk 1” Workaround: Read the related technical note. Go to www.ibm.com/software/rational/support/ and search for the text "upgrade insert disk 1.” |
||||||||||||||||||||||||||
| Internationalization | 237570
|
The default font used on the drawing surface is not suitable for all languages (especially Asian languages). Workaround: Users should change the default font
face in the Options dialog box (on the Tools menu)
by expanding Rational XDE and Appearance,
and then clicking General. Choose a font that supports
your character set. Also, select Default for
new models in the Settings for list to
ensure that the change applies to all new models. |
|||||||||||||||||||||||||
245756
|
An English-language error message appears when starting the Rational Unified Process, or RUP, and RUP's Extended Help, if you have not installed the Sun Java Runtime Environment (JRE) plug-in, version 1.4.1, for your Web browser. For a workaround, see defect 245756 under "General XDE." |
||||||||||||||||||||||||||
593705
|
Publishing a model to a folder that has double-byte characters in the name causes the tree control to fail in the published model. Workaround: Replace the default Sun Java Runtime Environment (JRE) version 1.3x with version 1.4.1_01. |
||||||||||||||||||||||||||
| Round-Trip Engineering | 135148
|
The Visual Studio .NET 2002 shell supports only 64 pages in the
Options dialog box (click Tools > Options). Each of
these pages is identified by a registry entry in the following
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.0\ToolsOptionsPages On a standard Visual Studio .NET installation with XDE installed, the number of Options pages exceeds the aforementioned limit. Therefore, the following two Rational XDE pages in the Options dialog box for Visual C++ settings may not be displayed:
As a result, it is not possible to configure the settings on the affected pages. Workarounds:
|
|||||||||||||||||||||||||
135490
|
If you create a project with Rational XDE models in Visual Studio .NET 2002, and then subsequently upgrade the IDE to Visual Studio .NET 2003, upon reopening the project, the Miscellaneous Files project in the Solution Explorer may appear to have duplicate versions of each referenced assembly model. This condition occurs after you reinstall XDE in Visual Studio .NET 2003, open up the project, and then synchronize the project or open the model. The apparently duplicate models are actually separate versions. After the upgrade to the new IDE version, both Visual Studio 2002 and 2003 versions of each referenced assembly model are shown under the Miscellaneous Files project in the Solution Explorer. Although the references to assembly models point correctly to the Visual Studio .NET 2003 versions (vs7rte\vsnet\Models\v1.1\*.mdx), the display of the apparent duplicate assembly models may be confusing. However, this condition does not affect synchronization or cause actual problems of any kind. Workaround: To remove unused duplicate reference models from the project:
|
||||||||||||||||||||||||||
136904 |
Visual Studio .NET 2003 (devenv.exe) may hang indefinitely when using Visual C++ support in Rational XDE 2003.06.12. This can happen when running on:
Workaround: If this problem occurs under this set of conditions, you must reboot the computer by turning it off and back on. This issue with the Windows 2000 kernel is Microsoft support case SRX031219604116. For the related Knowledge Base (KB) article and to learn about any hotfix, see article number 837443 at http://support.microsoft.com/?id=837443. IBM Rational customers can also contact Microsoft support directly for the hotfix, at the toll-free phone number(s) listed on http://support.microsoft.com, by simply referencing the KB article number (837443) for this problem. |
||||||||||||||||||||||||||
Error messages may appear during synchronization if you have reverted from the Rational XDE version 2003.06.12 Service Release to an earlier version of XDE. Workaround: Use the following procedure as a guide when synchronizing.
The next time you synchronize, the correct profile is applied. |
|||||||||||||||||||||||||||
137444 |
If you are using Rational XDE with Microsoft Visual Studio .NET 2003, you may see the following error message after using the Visual C++ Round-Trip Engineering feature in a solution containing a Managed C++ Windows Form project and adding a new form to the project:
The form fails to open up in the designer and the message appears in both the designer form and the task list. This error happens most frequently on Windows 2000 and is the result of an "out of memory" problem. Workaround: To free up contiguous memory:
|
||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
| Web Publishing and Reporting | 243697 |
If you filter out a particular element type (such as Text), hot spots that have no associated links may be created in the published model. Workaround: Remove all filters before publishing a model. |
|||||||||||||||||||||||||
375379
|
If you are linking an external file to a model element, you can
specify the file reference for the link with either an absolute path
or a relative path. File references that are specified with relative
paths do not publish to the Web correctly.
Workaround: If you want to publish a model to the Web, specify only absolute paths for all linked files. To specify an absolute path for a linked external file, do the following:
|
||||||||||||||||||||||||||
| General XDE | 232204 |
Synchronization between ASP.NET and XDE Web Services is not supported under Windows NT 4. This is a known issue with Visual Studio.NET and there is no workaround. | |||||||||||||||||||||||||
239560, 241074 |
When you import or export large models using the XML Metadata
Interchange (XMI) file format, the Rational XDE import and export process
may hang/stall or a java.lang.OutOfMemoryError message may appear. To
prevent the hang or error message, you must change the default Java Virtual
Machine (JVM) size setting from 256 MB to a larger size.
Use the following steps to increase the JVM size setting within the Registry:
Note: The actual size of the JVM should be smaller than the physical
RAM size of the computer, and must be multiple increments of 1K (or
1024 bytes). |
||||||||||||||||||||||||||
243239
|
When you export a Rational XDE model using the XML Metadata Interchange (XMI) file format, the following harmless error messages may appear if the ClassicRose profile is applied to the model you are trying to export and the model contains XDE-created realization and abstraction relationships:
The error messages appear because there is no UML:Realization metaclass in UML/XMI. On XMI export, Rational XDE realizations and abstractions stereotyped as "Realize" are exported as UML:Abstraction stereotyped as "Realize". On XMI import back into Rational XDE, all abstractions with “Realize” stereotypes become realization relationships in XDE. |
||||||||||||||||||||||||||
244167 |
If you upgrade your Microsoft Windows 2000 Terminal Server to Service Pack 4 (SP4) from SP3 and then try to use the Rational XDE version 2003.06.12 Service Release, you may experience a package load failure. Then, on exiting Microsoft Visual Studio .NET, you may get an application error:
This behavior happens when the following conditions are met:
Workaround:
This is a known Microsoft issue. Please refer to http://support.microsoft.com/default.aspx?kbid=823485. |
||||||||||||||||||||||||||
244643,
244687
|
When you export a Rational XDE model to the Unisys 1.3.5 file format, multiple state and final state actions (such as do, exit, and entry) are not exported. When you import the Unisys 1.3.5 file back into XDE, only one action (a do action) is imported. All actions (UninterpretedActions) should export and import correctly. Workaround: Remove multiple actions that reside within an activity model element before exporting a model in the Unisys 1.3.5 format. |
||||||||||||||||||||||||||
244776 |
You can add multiple events such as signals, calls, and time events
to a
transition in Rational XDE. However, when you export an XDE model that contains
transitions with multiple events to the Unisys 1.3.5 XMI file format, you cannot import the same model back into XDE.
Workaround: Add one event per transition when you want to associate multiple events with a transition. |
||||||||||||||||||||||||||
245150
|
If
you export a Change Event model element with the Change property
assigned to a specific string, the export representation generated in
the XMI file is incorrect. The attribute "body" is generated
twice, which causes the exported result to be incorrect syntatically.
Workaround: Change the duplicate attribute "body=" to "language=" in the exported XMI file. |
||||||||||||||||||||||||||
245408
|
Associating one constraint with multiple model elements causes XDE to hang during an XMI import. Workaround: Only associate one constraint with one model element. |
||||||||||||||||||||||||||
245427
|
Activity graphs with a SubactivityState reference export to an XMI file format correctly; however, when you import the XMI file back into XDE, the reference is not interpreted correctly. The imported model will not have an ActivityGraph reference for a SubactivityState. There is no workaround for this defect. | ||||||||||||||||||||||||||
245430 |
Object Flow States with a Classifier reference export to an XMI file format correctly; however, when you import the XMI file back into XDE, the reference is not interpreted correctly. The imported model will not have a Classifier reference for an Object Flow State. There is no workaround for this defect. | ||||||||||||||||||||||||||
245432
|
Call Events with an operation reference export to an XMI file format correctly; however, when you import the XMI file back into XDE, the reference is not interpreted correctly. The imported model will not have a operation reference for a call event. There is no workaround for this defect. | ||||||||||||||||||||||||||
The Rational Unified Process, or RUP, and RUP's Extended Help, will not work if you have not installed the Sun Java Runtime Environment (JRE) plug-in, version 1.4.1, for your Web browser. In addition, the related error message appears in English and is not localized. Workaround: Install Sun JRE 1.4.1. To install the JRE plug-in, do one of the following:
For other options, please contact your organization's technical support staff. When finished installing, restart RUP or Extended Help. |
|||||||||||||||||||||||||||
The following tables describe the defects fixed in this and previous service releases.
| Category |
ID |
Description |
| General XDE | 247693/APAR IC40927 |
Hotspots created for elements contained in swimlanes (whether merged or not) may not be placed in the expected location. |
|
Category |
ID |
Description |
| Documentation | 242208
|
The online Help for Data Modeling states that you can assign a domain to an attribute in a logical data model. This functionality is not supported. |
| Round-Trip Engineering | 136715
|
Rational XDE reverse engineers Microsoft Visual Studio .NET Web projects into a new model file with no contents from the source project. This issue was fixed by changing the Rational XDE HTML parser to
be case-insensitive when looking for HTML tags. If the parser is
unable to parse a file, it reports the error and continues with the
next file instead of aborting the synchronization. Writing of aspx,
asmx, and ascx files is now more robust on both VS.NET 7.0 and 7.1. |
137288
|
A reverse-engineered class is added to code within a code template expansion, leading to unexpected behavior. If a class has a code template bound to it, then a nested class, field, or operation added to that class in the model may get generated within the code template expansion in code during synchronization. This added item is deleted during code template expansion upon the next synchronization. |
|
137427
|
Having a code template bound to a class prevents a user from deleting elements in the class from the Model Explorer. The auxilliary synchronization performed on model elements with a code templates bound to them, or on model elements whose stereotype has been changed by the user, causes any deletions made by the user within that element in the model to be ignored upon synchronization. | |
244203/APAR IC37806
|
XDE code templates bound to classes causes data loss. The binding of a code template to a class while at the same time modifying a model element in the class (for example, adding a parameter to an operation) causes the class to be deleted upon synchronization. |
|
| Visual Trace | 241144
|
Visual Trace will cause Rational XDE to terminate at the start of a debug/run session if XDE is installed into a directory that contains Japanese or double-byte characters in the name. |
241476
|
If you are using Microsoft Visual Studio .NET 2003 and are a member of the the Debugger Users group in Windows, the list of classes you select for monitoring by Visual Trace wil not be retained once you close the Class Selection Wizard. |
|
447942 |
Visual Trace is not always able to differentiate between applications launched by a user and other processes started as a result of an IDE action. This can result in Visual Trace attempting to trace processes unintentionally and displaying the following warning: "Visual Trace supports only tracing one application at a time. Please stop all other applications being traced and restart the application." |
|
514577
|
The following defect is now associated with solution 187450534. Please refer to this number when calling technical support for additional information. Visual Trace uses a socket to connect to the application being traced. If a connection cannot be established, the following warning is displayed: "Visual Trace could not establish a socket connection with target." |
| Category |
ID |
Description |
| RequisitePro Integration | 59126, 238444 |
Using the Rational RequisitePro-XDE integration caused JVM error messages when closing Rational XDE. |
| Visual Trace | 241395, 514239
|
If you are using the Rational PurifyPlus or Visual Trace features to observe a program running under Microsoft .NET Framework 1.1, the observed program may crash with an "uncaught exception" message. If the error message refers to a library called BCIEngCOR.dll and includes the error code number 0x80000003 or the words "user breakpoint," then this error is caused by a known .NET Framework defect. |
The IBM software support Internet site provides you with self-help resources and electronic problem submission. The IBM Rational Software Support Home page can be found at www.ibm.com/software/rational/support.
Voice Support is available to all current contract holders by dialing a telephone number in your country (where available). For specific country phone numbers, go to www.ibm.com/planetwide.