09/02/2004
GI11-4684-03
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 Java editions of the IBM Rational® XDE™ Version 2003.06.13 Service Release. Because service releases are accumulative, this document also includes information about the previous service releases, versions 2003.06.01 and 2003.06.12. 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 (English version) and version 2003.06.10 (Japanese version), so please refer to the appropriate base document or see the release notes for new product installations of version 2003.06.13. Some information is specific to a product package, and is designated accordingly.
Note: This document is installed with the service release, to <install-location>\Rational\doc\xde_readme_java_sr.html. It 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. Search for "GI11-4684-03" to find the latest version of this document in the IBM Publications Center. (To search for the IBM Publications Center, go to www.ibm.com and enter "IBM Publications Center" in the Search field.)
Additional updates may be available for this service release. To determine if there is an update that applies to this release, take the following steps:
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 Java 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 Version 2003.06.12 Service Release provided the following major enhancements for the Java platform editions:
For Java Developer and Developer Plus Editions Only
For Rational XDE Developer Plus Edition Only
The earlier Rational XDE version 2003.06.01 Service Release provided new functionality and improvements in performance and usability, including the following:
This release has no additional hardware requirements beyond Rational XDE Version 2003.06.00 or 2003.06.10, or later service releases.
In Rational XDE 2003.06.13 Service Release
Expanded Microsoft Windows XP Professional support and added support for IBM WebSphere Studio Workbench 2.1.3, IBM WebSphere Studio Application Developer 5.1.2, and Eclipse 2.1.3.
| Supported Operating Systems | The following operating systems are tested and supported:
Notes:
|
| Supported Platforms |
|
In Rational XDE 2003.06.12 Service Release
This service release included new support for Windows NT 4, additonal databases, platform updates, and J2EE deployment updates. It also had changed Sun Java Plug-In recommendations.
| Supported Operating Systems | The following operating systems are tested and supported:
Notes:
|
| Supported Platforms |
|
| J2EE Deployment |
|
| 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. |
In Rational XDE 2003.06.01 Service Release
This service release included modified support for Windows 2000. In addition, it included a new requirement to support Web publishing and reporting in Rational XDE Developer - Java Platform Edition.
| Supported Operating Systems | The following operating systems are tested and supported:
|
| 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/. |
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.13 or higher.
This service release can be applied to the following editions of Rational XDE version 2003.06.00, 2003.06.01, and 2003.06.12 (including the Japanese-language version of 2003.06.12):
This service release cannot be applied to the Japanese-language version of Developer - Java Platform Edition, Rational XDE version 2003.06.10. Instead, a full installation is required. See Upgrade Installation Information for Version 2003.06.10.
Do not apply this service release to any evaluation versions of Rational XDE.
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.
This section applies to Rational XDE Developer and Developer Plus editions only. The following instructions have been updated to describe installation into an Eclipse 2.1.x shell.
| String name | Example value | Description |
installdir |
C:\Klips |
The location to which the Eclipse product was installed. This location always contains an Eclipse subdirectory. In the example, C:\Klips\Eclipse exists. |
name |
Klips |
The combination of name and version will be displayed in the selection list of shell instances during the install. In the example, "Klips 2.0" will be displayed. |
version |
2.0 (or 2.1) |
Append a comma and new value to the IDE_SHELL_DYNAMIC_OPTIONS= line in the .dat file, using the following format:
Eclipse:2.0:<registry key of Eclipse shell>:<text displayed to user>:<name to display in list of available host shells>
Using the Klips example presented above, you would append the following string to the IDE_SHELL_DYNAMIC_OPTIONS= line:, Eclipse:2.0:Klips:The Klips development environment.:Klips
Append a comma and new value to the IDE_SHELL_DYNAMIC_OPTIONS= line in the .dat file, using the following format:
Eclipse:2.1:<registry key of Eclipse shell>:<text displayed to user>:<name to display in list of available host shells>
Using the Klips example presented above, you would append the following string to the IDE_SHELL_DYNAMIC_OPTIONS= line:, Eclipse:2.1:Klips:The Klips development environment.:Klips
This service release does not apply to Rational XDE version 2003.06.10 (Japanese version). In order for users of Rational XDE version 2003.06.10 to upgrade to this service release, version 2003.06.13, the following is necessary. First, uninstall Rational XDE version 2003.06.10. Then, install this service release.
To upgrade from Rational XDE version 2003.06.10 to version 2003.06.13:
If needed, see Reconfiguring XDE into a Different IDE, below.
You can find the latest version of the Upgrade Guide at ftp://ftp.software.ibm.com/software/rational/docs/documentation/manuals/suite.jsp.
This service release upgrades all earlier installed version 2003.06.00, 2003.06.01, and 2003.06.12 Rational software products (this is not selectable). It will upgrade Rational XDE only if you have version 2003.06.00, 2003.06.01, or 2003.06.12. 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.
In addition to applying the service release to upgrade your existing Rational XDE installation, you can also reconfigure XDE into a different IDE. For example, you can migrate your current IDE integration to version 5.1 of IBM WebSphere Studio Application Developer, or to the latest WebSphere Studio Workbench included with XDE, version 2.1.2.
There are two approaches to reconfiguring the IDE used by XDE. The more straightforward is to remove the current XDE installation and then reinstall XDE into the new IDE. The other approach is to install the service release and then use a utility that is available from Rational to reconfigure the XDE shell integration. There are more steps involved in this latter approach, but it allows ongoing reconfiguration.
Use one of the following approaches to reconfigure the shell for XDE:
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
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.
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.
Rational XDE is installed with several text editors that have varying capabilities and interfaces. This selection of editors gives the user a great deal of choice in how to view and edit code.
Note that you can also click the Add button to add a file type that is not listed.
Rational Rose ANSI C++ models can be imported to Rational XDE. Additional infomation on importing Rose models into XDE can be found in the online Help installed with XDE.
XDE and Rose Concepts
XDE works differently from Rose in a number of ways, but the most relevant are:
File Locations
XDE requires that new files be created in a directory below the project root. For instance, if you create an XDE C++ modeling project in the directory C:\myproject, new files are then created below the myproject directory.
When importing a Rose model into XDE, it is recommended that the XDE project be created in a directory that contains all the Rose source code in order to fully take advantage of the XDE product's code-browsing features. For example, if the Rose project uses source code in the directories C:\rose-project\juniper and C:\rose-project\yew, then the XDE project should be created in C:\rose-project.
Project Constraints
It is essential that XDE projects not overlap. An XDE project contains references to all file resources in the directory tree below its location (the project root). XDE does not allow multiple projects to contain references to the same resource.
You cannot have two XDE projects in the same project root. You can also not have a project in a subdirectory of another project's root directory.
Multilanguage Projects
Rose supports projects with multiple implementation languages; that is, multiple language classes can coexist in one Rose model. If this type of model is imported to a C++ project, all the classes are converted to the C++ code model, but the Synchronize property for non-C++ classes is set to Excluded so that they do not participate in round-trip engineering.
The Java/J2SE add-in does not currently support round-trip engineering of Java files that are "linked resources"—that is, .java, .class, or .jar files that are themselves defined as linked resources, resources that are outside the project itself but referenced through the linked resource path variables, or resources that are contained within a folder that is a linked resource.
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 Rational XDE 2003.06.01 Service Release added Web publishing and reporting capabilty for the Rational XDE Developer - Java Platform Edition. The restrictions and guidelines listed in the release notes for Rational XDE 2003.06.00 also applied to these users. For more information, see Rational XDE Version 2003.06.13 Release Notes for new product installations.
The following tables describe the known issues in this and previous service releases.
|
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. |
|
| General XDE | 247316 |
When using Rational XDE version 2003.06.13 with WebSphere Studio Application Developer 5.0.x, an error message may be displayed upon exiting XDE. Workaround: Although the workspace is not affected, you can prevent the errors by upgrading to Application Developer 5.1 or above. |
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 |
|||||||||||||||||||||||||||
| C++ | 245816 |
You
may be unable to close the C++:
Add Source files dialog box because of a reappearing error message
dialog box. This happens if you click the Add Files button
and enter a nonexistent directory name, and then click the Add
Recursive button.
Workaround: The C++ Add Source files dialog box can always be closed by pressing the ESC key. |
|||||||||||||||||||||||||||
| Configuration Management | 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. XDE customers who also use the WebSphere Studio Application Developer 5.1.x UML Diagramming feature should contact IBM Rational Software Support for assistance. |
||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
| Documentation | 243667
|
The
Javadoc version of the RXE API documentation does not reflect the inheritance
model used in the Patterns and Code Templates portion of the API. The
actual inheritance used is as follows (indentation indicates inheritance.)
|
|||||||||||||||||||||||||||
245889/APAR
IC39101 |
See the description for defect 245889 above, in the "Data Modeler" section of this table. | ||||||||||||||||||||||||||||
453915
|
In Rational XDE Help, an incorrect description is included in the topic “Defining Code Template Bodies.” Workaround:
In this topic, within the "For a Body Kind of Java" section,
the interface name IRXECTCallOutUser should be replaced with IRXECodeTemplatesExpansion. |
||||||||||||||||||||||||||||
| Installing and Uninstalling | When installing into IBM WebSphere Studio Application Developer version 5.1.1, it may be necessary to upgrade the underlying Java Runtime Environment (JRE). To determine whether an upgrade is necessary after installing this service release, you must check the two build identification numbers associated with the JRE within WebSphere Studio Application Developer.
You do not need to upgrade the JRE if the following versions are returned:
If you see any other numbers, then the JRE was not upgraded and you must do the upgrade manually.
Workaround: Manually upgrade the JRE by manually
copying the following directory to the jre directory within WebSphere
Studio Application Developer 5.1.1: This directory includes all the files required to upgrade the JRE. |
||||||||||||||||||||||||||||
Under Windows NT, XDE may fail to install into WebSphere Studio Application Developer 5.0.1 if the value for the NT 4 registry size is less than 40. Workaround: Set the NT 4 registry size to 41 or more: Right-click My Computer, click Properties, click the Performance tab, click Change under Virtual Memory, and set Maximum Registry Size to 41 or greater. |
|||||||||||||||||||||||||||||
| 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 Preferences dialog box (on the Windows 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." |
||||||||||||||||||||||||||||
| J2EE | 243880
|
When
the web.xml file declares more than one filter URL pattern and the
file is externally modified to delete a URL filter pattern, the tag
editor does not update the file correctly. The web.xml file is invalid
because
an empty tag exists representing the deleted filter URL pattern. The
errors occurs on reimporting the modified web.xml file.
Workaround: In the Web deployment model, select the servlet filter with the externally removed Web filter URL pattern. Then, in the Properties window, open the tag editor for the WebFilterURLPattern property, click OK, and close the tag editor. This triggers the system to clean up the blank Web filter URL pattern. |
|||||||||||||||||||||||||||
243962
|
The deployment descriptor editor for IBM WebSphere Studio Application Developer does not always refresh immediately after a Rational XDE-Application Developer synchronization. As a result, changes made from XDE may not be visible in Application Developer until the user closes and reopens the editor. For example, when a CMP field is added to an Entity Bean in XDE, the new CMP field is shown in the J2EE hierarchy, but not the CMP field section of the Bean tab. Workaround: Close and reopen the editor. |
||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
| Visual Trace | 135408
|
The IBM Java Runtime Environment (JRE) that ships with the IBM WebSphere Studio Application Developer platforms prior to version 5.1 does not provide the ability to use Visual Trace when running in debug mode. As a result, users of the Rational XDE Developer Plus for Java Platform Edition who engage Visual Trace will not produce a trace sequence diagram when J2SE applications are run in debug mode. Workaround: An updated version of the JRE is included
with the XDE product media. For installation instructions, see the
related "Installation Issues" note above.
Alternatively, you can upgrade to Eclipse version 2.1 or WebSphere
Studio Application Developer version 5.1. |
|||||||||||||||||||||||||||
137862
|
IBM WebSphere Studio Application Developer crashes when IBM Rational XDE is being used to try to display a sequence diagram from a trace of an application that contains a very long method signature of more than 1,000 characters. | ||||||||||||||||||||||||||||
| 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. |
|||||||||||||||||||||||||||
245328 |
If you try to publish a model without having the Java Runtime
Environment (JRE) installed, XDE displays a message that prompts you
to install the 1.3.1 release of Java Plug-in Software. After installing
Java Plug-in 1.3.1, when you try to publish a model, XDE displays the
following error message:
Workaround: Install the 1.4 release of Java Plug-in Software before or after installing XDE. |
||||||||||||||||||||||||||||
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 | 44806 |
When you open a dialog box to browse to a folder in IBM WebSphere Studio Workbench on Windows NT 4, the dialog box may lose focus and be obscured by other dialog boxes. Workaround: Use Alt + Tab change focus or click the desired dialog box. This a known issue for Eclipse running on Windows NT. |
|||||||||||||||||||||||||||
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. |
||||||||||||||||||||||||||||
244103 |
If you click a class shape in the diagram window, then click
the diagram surface and click a class shape again,
the check marks displayed in the Show/Hide
Compartment list on the Appearance toolbar
do not update to show which compartments are currently visible on the
last class shape
selection.
Workaround: Change the selection directly from one class shape to another class shape to display the correct settings or select another class shape and then reselect the desired shape to update the list. |
||||||||||||||||||||||||||||
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. |
||||||||||||||||||||||||||||
245197 |
If you are running Windows 2000 and have installed the Japanese version of this service release into the IBM WebSphere Studio Application Developer version 5.1.1 shell, the Help window may become corrupted or hang if you switch between the Help window and other windows. Workaround: Close the Help window and restart the shell. The next time you use Help, it will work normally. |
||||||||||||||||||||||||||||
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. |
|||||||||||||||||||||||||||||
Note that the Web publishing and reporting issues now apply to all Java platform editions in the Rational XDE 2003.06.01 Service Release.
The following tables describe the defects fixed in this and previous service releases.
|
Category |
ID |
Description |
| Compare/Merge | 238097
|
If you attempt to use the Compare With > Each Other menu command when all of the resources selected in the Navigator are XDE artifacts, the shell will appear to hang. The operation may finally complete, provided you have adequate physical/virtual memory, but it may take hours or days to run. |
239447
|
If you end a ClearCase-initiated merge session by clicking the Close button, you may see five error messages. To avoid this, please follow the recommended procedure for ending a merge session, which is to use the File > Compare/Merge menu instead of the Close button. |
|
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. |
|
513872
|
The following defect only applies to the Rational XDE Developer - Java Platform Edition: A ClearCase-initiated merge session will fail while comparing or merging two interaction instance units (*.iix), containing at least one lifeline, with each other. |
|
| Configuration Management | 239403
|
When opening a read-only (for example, controlled and checked-in) model created using a previous release of XDE for the first time, and the model is a non-Java Code Model with the Java profile applied, you will see the following error message in the output log: Error: Exception in MU.doTaggedValues(NME): This error is benign and can be safely ignored. After continuing with the upgrade of the model and saving it, you should not see this error again. |
239945
|
Users who go off-network will not be presented with the view chooser
when using the Rational XDE |
|
|
239946
|
Users who created cross-model references that resolve through XDE version 2002, Release 2.1 Service Release VOB-root registered locations must use a snapshot view the very first time these models are opened in XDE version 2003.06.00 or later, which will result in these models being upgraded. Once the models are upgraded and checked in, the models can be accessed in a ClearCase dynamic view. | |
240185
|
Opening a model containing cross-model references in a ClearCase dynamic view may result in the following behavior: Any models that are opened in the process of resolving the cross-model references are not shown as being under source control in the Model Explorer (they do indicate as being source-controlled in the Navigator). |
|
246156
|
It is possible for newer versions of a model to be loaded during a rebase, update, or deliver operation; therefore, we recommend that the user do the following when performing one of these operations:
|
|
513516, 513549
|
When changes are made quickly during a rebase, the reload prompt
will not appear. If you quickly move between a model check-in and a rebase
(that is, in less than a minute), this may result in a situation where
the software does not recognize that a change had been made.
Steps to reproduce the problem:
When steps 2 through 7 occur in less than a minute, the described problem occurs. However, such a scenario is rare and would require unusual speed and coordination. |
|
514052
|
When a user tries to add newly created and unsaved storage units to source control, the storage units may not be listed in the Add to Source Control dialog box. This issue arises if Do Nothing is selected for the team/Rational ClearCase preference setting When new resources are added. |
|
| Data Modeling | 241098
|
If you have no existing data model, the Class to Table Transformation dialog box does not open when you use the Class to Table command on the Transform menu. |
| Documentation | 246175
|
See the description for defect 246175 below, in the "General XDE" section of this table. |
| The Help for Visual Trace should include the following text: "You must engage Visual Trace before starting the application to be traced." | ||
| Installing and Uninstalling | When uninstalling Rational XDE version 2003.06.12, two DLLs may be removed that are required but not reinstalled if you install another version of XDE, including version 2003.06.00. |
|
239910
|
After you import a Rational Rose model (*.mdl) to a Rational XDE model (*.mdx), immediately save the imported model to the XDE file format. If you attempt to modify the model without first saving it as an XDE model, and then select Cancel from the Save As dialog box, the model will be closed without saving the changes to the model. | |
| The following issue only applies to the Rational XDE Developer Plus Edition: To correctly configure a SitePrep area for XDE, Rational recommends that you do not use SitePrep.exe directly. Use Setup.exe and select Enterprise Install mode to create the SitePrep area. If you use SitePrep.exe directly, the SitePrep area may not be properly configured and an install performed from the improperly configured area may hang. | ||
| Internationalization | 240169,
240232
|
XDE cannot be installed into a path that includes Japanese or double-byte characters. |
453121/APAR IC38562
|
If a file is updated during code generation, a space is appended to the end of the file for each Japanese character in the file. This happens every time the file is updated on code generation. |
|
453933
|
The XDE-supplied file RASRepositoryService-portable.war, provided as part of the J2EE RAS Repository, does not support internationalization requirements. When you create a J2EE-type repository service with this file, any Japanese characters in the assets owned by the repository will display as question marks (?) in 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. |
|
| Java | 49893
|
When automatic synchronization is enabled, XDE will synchronize a project's Java code model to any changes you make to the project's .java files. If you make a change when the code model is closed, it will be opened and the XDE Model Explorer view will get focus. For instance, you are in the Navigator view and you delete a .java file from a project whose code model is closed. The model is opened in the Model Explorer, which will take focus away from the Navigator. |
134804
|
The project name is not displayed when creating a Java modeling project for the first time in the Model Explorer. The project name only appears after performing any Java action such as creating a Java element or synchronizing source code and the model. | |
245085/APAR
IC38424
|
If two packages contain a class with the same name and you attempt to move one of the classes into the package with the conflicting class by changing its package statement and then synchronizing (or if you perform this change with autosync enabled), the move of the class will fail. At the point of failure, the output log will indicate that there was a failure to rename the class. The Model Explorer will then show a new class and component with "_1" appended to the name. In addition, you will see a component with "_1" appended after ".java" |
|
|
589683 (54005)
|
The UML Subsystem element is not supported in Java code models. Its use will cause errors during round-trip engineering. | |
| J2EE |
234444
|
When modeling J2EE applications, use separate projects and code models to model EJB, Web, and client components, including clients used to test one of the other "tiers." (Note that WebSphere Studio Application Developer forces you to use this structure.) By default, when you create deployment models, they automatically get «JARinclude» relationships to the corresponding code models. This step conveniently associates the components to the corresponding JAR. However, if you have servlets and EJBs in the same code model, all of them will get included in the EJB-JAR and WAR that you create. This is a problem when you deploy both tiers to the same machine. Many application servers use the same classpath for both tiers. So, for example, when you invoke a servlet, you may get the servlet located in the EJB-JAR and not the servlet in the WAR. This is especially confusing if the servlet has changed since you last built and deployed the EJB-JAR. |
237932
|
When you reverse engineer an EJB or Web deployment descriptor, some relationships between elements on existing diagrams may be inappropriately deleted from the diagram. To restore a missing relationship, remove one of the two "end" elements from the diagram (do not remove it from the model), and then add it back to the diagram by dragging it from the Model Explorer. This step will redraw the line. For EJB diagrams, the shortcut menu command Customize EJB Diagram can also be used to restore these lines. | |
239887, 229151, 239854
|
In some scenarios, the method filtering in EJB diagrams does not work as expected.
|
|
239960
|
The J2EE patterns code templates that are inserted for method bodies are not marked "first-time-only expansion." Hence, every time you synchronize or forward engineer, the code template will be inserted, replacing any code that you added after creating the EJB, servlet, etc. This causes problems for methods that you must change manually. |
|
| Saving in the J2EE perspective deployment descriptor editor or
importing ejb-jar.xml deployment descriptors can result in corrupted
EJB Relationships in XDE under certain circumstances. If the name of
the CMR field ("cmr-field-name" in the descriptor) is the same
as the name of the relationship role on the other end of the
relationship ("ejb-relationship-role-name"), then XDE will
corrupt the relationship, requiring that it be deleted and recreated.
This duplication in naming is the default for CMRs that are in upgraded
models from earlier releases of XDE. When creating CMRs in XDE and WebSphere
Studio Application Developer, both use different names for these elements
by default. However, if you explicitly use the same name, the problem
will occur. |
||
243758
|
When using Rational XDE with IBM WebSphere Studio Application Developer 5.0.x and synchronizing a Run As security role in the EJB deployment model, the role is not updated in Application Developer. |
|
| Patterns and Code Templates | 57755
|
Facade Pattern : Duplicate return type. |
|
135407
|
Bindings of external code templates in models from earlier versions of the product are not being upgraded correctly. After model upgrade, the external code template bindings are still functional in the upgraded model; however, the bindings are no longer suitable for use in situations where the path from the model to the external code template needs to be indirect. Typical situations where this occurs would be when a model is under configuration management and different users view the code template using different paths, or when the code template binding is copied from one model to another via using a pattern application. |
|
| RXE | 239228
|
For generalization, dependencies and realizations, the methods/properties to access the end elements return the opposite end. Specifically:
|
240004
|
The methods IRXEReference.Resolve() and IRXEReference.getRefModel() always return Null. A call to resolve() will resolve a reference, if possible, but it will still return Null. |
|
| RXE (Patterns and Code Templates) | 51254
|
When called from a patterns OnBind callout, the RXE pattern’s getPatternInstance() method returns null when it should return the pattern instance. |
| Web Publishing and Reporting | The publishing function requires the Java Plug-in. The Java Plug-in is not included in the Rational XDE installation. | |
241330
|
If you are using an installation of Rational XDE that was installed by another user, you may be prompted to install additional components when you attempt to publish a model. The suggested installation is unnecessary; you should click Cancel. Publishing will then proceed normally. If you allow the process to finish by not clicking Cancel, a second dialog box appears that suggests a restart. You should click No. If you click OK, XDE restarts and the published model is incomplete. |
|
372979
|
In a published model, displays that rely on a relationship with a MessageEnd object fail. These failures include:
|
|
374690
|
If you publish a model that includes global actions, those actions are not represented in the published model. | |
| General XDE | 238301
|
The cross-model reference adornment is not displayed in the correct position in the print preview or when you paste the shape into other applications such as text editors. |
238555
|
When you open a saved model that initiates specific internal processes to open a diagram, the model appears in the unsaved or modified state (with an asterisk next to the model name in the Model Explorer), even if you made no modifications to the model. You can safely save or discard the changes without data loss. |
|
238740
|
When you work with subunits, it is recommended that you save your work by using the Save All command on the File menu. If you use the Save command (or Ctrl+S), your work may not be saved consistently. For example, you may change one subunit, which results in changes in two other subunits. If you save only the first subunit and not the two others, the files saved on disk will be inconsistent with one another. If, instead, you use the File > Save All command, all three changed files will be saved to disk and the files on disk will be consistent with one another. |
|
240261
|
When renaming a model with separate subunits, ensure that all documents currently open on the model are closed prior to the rename. If the documents are not closed first, the separate subunit links will be broken in the model. | |
241211
|
This defect shows up in two scenarios:
|
|
241325
|
During the model upgrade process (especially with non-US English models), the XDE print preferences may not upgrade correctly. | |
241771
|
Users who have installed Rational XDE Developer Plus on Windows NT may find that saving a blank model assigns a Rational RequisitePro applied profile to the model. |
|
When you import a model file from Rational Rose into Rational XDE, classes that have stereotypes may become very large in the diagram window. |
||
After you use Rational SoDA to generate a report on an XDE model, you may be unable to open diagrams in XDE and you may see a variety of error messages. |
||
If you are running Rational XDE on Microsoft Windows NT, you may see the following error message when attempting to launch Extended Help from the Help menu: "Extended Help is currently not available." |
||
514427
|
Changes to model subunits will be lost if a model is renamed without being saved first. |
|
518939
|
If you are using Rational XDE installed into Eclipse 2.0, you may see the following issue. A redundant Save As dialog box appears when you save a model with the focus set on the diagram window. | |
589765 (55216)
|
If you use the High Contrast display option for Windows 2000 Accessibility, the cursor is not visible in Rational XDE diagrams. | |
594382 (82893, 80803)
|
In some cases, you must rename a newly created activity graph or state machine, or you must close the model that contains it, before you can delete the activity graph or state machine. |
|
Category |
ID |
Description |
| Data Modeler | 241752
|
Creating new triggers for a table or view will cause an exception if the name of the respective table or view is less than 3 characters in length. |
| 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. |
| RXE (Patterns and Code Templates) | 51339
|
The operation getRXE() fails in the Visual Basic PreExpand callout. It may also fail in other Visual Basic RXE callouts. |
51437 |
In pattern callouts related to the use of the Apply Pattern
Wizard and Apply Pattern dialog box, the |
|
134788 |
Unable to successfully query for the Type value of the CTArgumentValue in a pattern callout so the callout fails. |
|
134973
|
A pattern’s template parameters can have both a collection value source and a user value source. Patterns with both value sources and only user argument values (no collection values are generated), cause a callout’s RXE lookupParameterValues() method to incorrectly return null. Expected return is an array of CTArgumentValueHolders containing the user-entered values. |
|
135069
|
In the Patterns OnBind callout, getThisElement() should return the pattern template because that is the element to which the OnBind callout is attached (the pattern template "owns" the onBind callout). Unfortunately, getThisElement() is returning the model in which the bound collaboration (pattern instance) is located. |
|
| 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. |
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." |
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.