Version 2002.05.21 Release 2.1
March 14, 2003
Copyright © 2003 Rational Software Corporation. All Rights Reserved.
This documentation (the “Work”) is protected under the copyright laws of the United States and/or other jurisdictions, as well as various international treaties. Any reproduction or distribution of the Work is expressly prohibited without the prior written consent of Rational Software Corporation.
This document contains release notes specific to the Rational XDE v2002 Release 2.1 Service Release, which primarily provides improved integration with Rational ClearCase. This document is meant to supplement the Rational XDE v2002 Release 2.1 Release Notes, so please refer to both documents.
Note: This document is installed with the Service Release, to <XDE-install-directory>\xde_readme_java_sr.html. To be sure you have the latest available information, Rational Software recommends that you check back for newer versions of this document at http://www.rational.com/support/upgrades/xde.jsp.
This release does not support all the software and hardware configurations that Rational XDE v2002 Release 2.1 supports. Please read the following requirements carefully.
This release has no additional hardware requirements
beyond Rational XDE v2002 Release 2.1 (2002.05.20).
| Operating Systems | The following operating systems are tested and supported:
In addition, both Microsoft Windows 2000 Server and Windows 2000 Advanced Server are supported. Notes:
|
| Operating System Languages | Level 2 support for German, French, Italian, and Swedish. (Supports local character set or English in fields, forms and documents; supports locale-specific conventions for date/time formats, numbering, and currency.) Level 1 support for Dutch, Hebrew, Japanese, Simplified Chinese, Traditional Chinese, and Korean. Notes:
|
| Supported Platforms |
This Service Release has not been tested with and does not support IBM WebSphere Studio Application Developer, Integration Edition, V4.1.1 (WSS AD IE). Notes:
|
| Internet Browser | Internet Explorer 5.5, Service Pack 2, or higher must be installed on your system. However, you can use other browsers, such as Netscape 6.0, to view published models. |
| Web publishing and reporting | Web publishing and reporting requires the Java Plug-in, downloadable from the Sun Web site at http://java.sun.com/products. |
| EJB, Web Modeling, and Deployment | One of the following platforms and their libraries:
|
| Rational RequisitePro | To use the Integrated Use Case Management (IUCM) integration of Rational RequisitePro and Rational XDE, you must have RequisitePro, Version 2002.05.20 installed on your system. |
| Configuration Management Software | Supports Rational ClearCase v.2002.05.00 and ClearCase LT v.2002.05.00, with patch levels as listed below. ClearCase 4.2 and ClearCase LT v.2001A.04.00 have not been tested and are not supported. Notes:
Prior to deploying this Service Release, your ClearCase installation must include all mandatory patches for your version of ClearCase, or XDE will not run. Current patch requirements are as follows:
To verify the latest patch information for your version of ClearCase, go to http://www.rational.com/support/downloadcenter To find out which patches your ClearCase installation has installed, use the cleartool -version command in a DOS command prompt window. |
This Service Release includes documentation and tools to enhance your team development experience with Rational XDE. This content is installed into two new directories. These directories are created under the Rational XDE installation directory, which is typically c:\Program Files\Rational\XDE. The new directories are:
The detailed walkthroughs demonstrate how to set up a combined Rational XDE and Rational ClearCase environment. These can be used as demonstration, evaluation, or learning exercises to understand the issues and procedures for setting up a combined solution. The scenarios cover base and UCM ClearCase integration with Rational XDE. There is also a summary document that describes the overall configuration options implemented by the scenarios.
| If you use Rational XDE | See |
| in any ClearCase configuration | Using XDE with ClearCase: Configuring Your Environment (summary-config.pdf) - This document summarizes the scenario setup environment when using XDE with ClearCase. The recommendations include tool options and configurations. |
with base ClearCase and IBM WSS AD |
Guidelines for Using Rational XDE and Base ClearCase with IBM WSS AD (xde_java_baseCC.pdf) - This guide helps you set up and work in a scenario that demonstrates the team development capabilities of Rational XDE for WebSphere Studio Application Developer (WSS AD) and base ClearCase. If you have installed the Rational XDE WebSphere Studio Workbench (WSWB) edition, you can use this scenario with only minor changes, including small differences with the screen shots. |
| with UCM ClearCase and IBM WSS AD | Guidelines for Using Rational XDE and UCM With IBM WSS AD (xde_java_ucm.pdf) - This guide helps you set up and work in a scenario that demonstrates the team development capabilities of Rational XDE for WSS AD and UCM. If you have installed the XDE WSWB edition, you can use this scenario with only minor changes, including small differences with the screen shots. |
The ClearCase XDE Type Manager Installer is an MSI installer that automates the setup steps required to properly configure the XDE Type Manager for ClearCase. This installer must be run on all client workstations. Note that the installation is triggered by XDE startup if it detects an improper type manager configuration. Additionally, UNIX versioned object base (VOB) repositories must be properly configured. For more information, see the Rational XDE Help topic "Comparing and Merging in ClearCase."
Rational XDE supports dividing models into multiple physical files, called subunits. This capability is very useful in allowing multiple users to modify various parts of the model concurrently. However, since modifications in one part of the model can result in modifications in other parts of the model, it is important that all related modified units be synchronized and managed as a single logical unit for configuration management purposes at key delivery points into configuration management (CM).
Prior to this Service Release, there was no automated support for treating models as a composite object. This Service Release introduces composite object versioning (COV) operations that facilitate the management of a model and all subunits in it linked to user gestures that perform various CM operations.
The general purpose of COV is that operations performed on a single or subset of subunits expands to include the entire file closure of the model. For example, if you have a model with two classes, class1 and class2, which are both stored as separate subunit files (class1.clx and class2.clx), and both class files are checked out, and you attempt to check in just class1, the checkin automatically expands to include both class1 and class2.
COV is turned off for models that are not open (not visible in the Model Explorer). If a model is not open, checkin operations behave as they did prior to this Service Release; that is, the checkin will apply only to the selected subunits and will not expand.
COV applies within a single model only. Operations do not expand across cross-model references to include all the referenced models.
The CM operations include: checkout, checkin, undo-checkout, update, and add-to-source-control. Differences between these operations as launched from the Navigator rather than from the Model Explorer are also included.
If you are connected to ClearCase, which is the default setting in this Service Release, you will be prompted to add all model subunits to source control when they are saved to disk. If you choose not to add them to source control at that time, they remain as view-private files, but the root model contains references to the subunit files. When any unit is checked in, a dialog box appears listing the view-private subunits, and it indicates that they all must be added to source control prior to completing the check-in of the requested file. The message wording begins, "The checkin operation has failed because, to ensure model integrity ..."
This check is triggered by both checkin and add-to-source-control operations. No checkins are allowed until the entire set of subunits is in the VOB. The Add Element(s) to Source Control dialog box would appear, for example, from an expanded add-to-source-control operation generated when a user tried to add a single unit to source control from the Model Explorer while the model contained several units marked as view-private.
Once all the units are checked in, these dialog boxes are not displayed when saving subunit files in the model.
Checkout is unaffected by these changes. Users can check out individual unit files without any expanding behavior. Checkout remains fine-grained and unchanged from Rational XDE v2002, Release 2.1.
Undo-checkout is unaffected by these changes. Users can undo the checkout of individual unit files without any expanding behavior. Undo-checkout remains fine-grained and unchanged from Rational XDE v2002, Release 2.1.
Attempts to check in a subunit or subset of subunits results in the closing of all files in the model being processed, and any subunit that is checked out that was not explicitly requested will be added, or the checkin operation will be expanded to include all files. You can choose to ignore the suggestion and check in only the units you specified, or cancel the entire operation. The calculation of the file closure also detects view-private units that have not yet been added to source control. If any of these are detected, a dialog box is displayed indicating that no checkin can be performed until all view-private units are added to the VOB.
In general, updating single model files or small sets of subunits is not recommended. This practice can lead to root nodes being loaded that have dangling references to missing subunits, or other model data representation issues. Therefore, COV has been extended to ensure that an attempt to update part of the model results in the entire model being updated.
To update, you right-click an element in the Model Explorer or Navigator and then click Update on the ClearCase shortcut menu. The resulting file closure expansion is displayed in the Update elements from source control dialog box.
In this Service Release, the Rational XDE startup process has been modified to perform a number of checks and enhancements to allow multiple-view, team-oriented development to occur with less manual intervention. When Rational XDE is integrated with Rational ClearCase, the following additional functions are performed when XDE is started:
This Service Release adds support for deployment of J2EE applications to WebLogic version 7.0.
The following changes have been made to the pages in the Preferences dialog box:
While viewing diagrams within models, it is important for the user to easily determine whether or not the model elements residing in one model have external references to different models. In this Service Release, these cross-model references are now indicated with an overlaid arrow glyph. This will aid the user in understanding the dependencies between models and the implications resulting from modification of these references.
To determine the build ID of Rational XDE that you currently have installed, run the Rational Software Installed Product Information utility by clicking Start > Programs > Rational XDE release-name > Rational Software Installed Product Information.
This Service Release can be applied to build 2002.05.20.516.009 of the following editions:
This Service Release does not support the Japanese-language version of the above editions, specifically:
Do not apply this Service Release to any evaluation versions of XDE.
The Rational XDE Service Release will only install on computers with Rational XDE v2002, Release 2.1 running on Windows 2000 or higher. If the Service Release installer is run on a machine that does not meet these requirements, the install will abort. The installer will automatically detect your Rational XDE installation and configure itself for the requirements of that installation.
To install the Service Release:
You can determine whether this Service Release has been installed by using the Add/Remove Programs utility. The Rational Software Installed Product Information utility does not provide this information.
To determine whether the Service Release has been installed:
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, first uninstall the Service Release, then uninstall Rational XDE, then reinstall Rational XDE. Uninstalling the Service Release without uninstalling Rational XDE is not supported.
Notes:
Follow these instructions to fully uninstall the Rational XDE 2.1 Service Release:
Note: Uninstalling Rational XDE will generate many errors that can be safely ignored. These errors are generated because uninstalling the Service Release removed many of the files the uninstall application is attempting to remove.
To ensure that Rational XDE and ClearCase integration is properly enabled, installation order is important. Install ClearCase, then Rational XDE Professional v2002: Java Platform Edition. For more information about this known issue, see "ClearCase Menu in XDE Fails to Appear When Installing XDE First, Then ClearCase," defect ID 510705.
Rational Software recommends using snapshot views when using Rational XDE with ClearCase; this Service Release has not been extensively tested with dynamic views.
If you are using Rational XDE together with ClearCase, you must rebase any streams before uninstalling Rational XDE.
After a rebase or deliver operation with identical changes made to the same UML model subunit by multiple users, duplicate UML elements occur in the resulting model.
When two users add a class with same name in the model (or under the same package) in their respective views, the Compare and Merge tool merges these elements automatically and the resulting model will have duplicate classes (in certain cases the diagram may also have duplicate classes). The Validate model command will then generate the following task item.
More than one Class in Model <<model_name>> has name <<class_name>>.
Resolution: Delete the duplicate class in the model.
When two users generate code or synchronize a class (which has no corresponding component in the current baseline) with same name in the model (or under the same package) in their respective views, the Compare and Merge tool merges these elements automatically and the resulting model will have duplicate components. The Validate model command will then generate the following task item.
More than one Component in Model <<model_name>> has name <<javafile_name>>.
Resolution: Delete the duplicate component in the model.
When two users add an attribute (with the same name to the same class) the Compare and Merge tool merges these elements automatically, and the resulting model will contain duplicate attributes. Validate model command will then generate the following task item.
Attribute(s) named <<attribute_name>> conflict in Class <<class_name>>
Resolution: Delete the duplicate attribute.
When two users add an operation (with the same name to the same class) the Compare and Merge tool merges the elements automatically, and the resulting model will contain duplicate operations. Validate model command will then generate the following task item.
Operation(s) "<<operation_name>>([retval]void)" in classifier <<class_name>> have conflicting signatures.
Resolution: Delete the duplicate operation.
When two users add getters and setters to the same attribute of the same class, the Compare and Merge tool merges these elements automatically, and the resulting model will contain an attribute with duplicate getters and setters. The Validate model command will then generate the following task item:
Operations "get<<attribute_name>>([retval]int)" in classifier <<class_name>> have conflicting signatures.
Operations "set<<attribute_name>>([in]int,[retval]void)" in classifier <<class_name>> have conflicting signatures.
Resolution: Delete the duplicate getter and setter
When two users add an attribute (with the same name to the same class) and then add getters and setters to the attribute, the Compare and Merge tool merges these elements automatically, and the resulting model will contain duplicate attributes and duplicate getters and setters. The Validate model command will then generate the following task item.
Attribute(s) named <<attribute_name>> conflict in Class <<class_name>>
Operations "get<<attribute_name>>([retval]int)" in classifier <<class_name>> have conflicting signatures.
Operations "set<<attribute_name>>([in]int,[retval]void)" in classifier <<class_name>> have conflicting signatures.
Resolution: Delete the duplicate attribute. This deletes the duplicate getter and setter. If both the getters and setters get deleted, you will need to regenerate them.
When two users change the same element during the Compare/Merge, the Ancestor tagged value will show a conflict and ask to be resolved. This tagged value should be cleared before this point, and not cause a conflict.
Resolution: It is safe to ignore this conflict. After the merge is complete, the Ancestor property is cleared.
If you are using an integrated Rational XDE-ClearCase configuration, please
ensure that you save your project set before installing this Service Release.
After installing the Service Release, you will need to work from workspaces
collocated with their corresponding ClearCase views. You can use the Add
Project Set to Workspace command to restore the contents of your workspace.
To save your project set before installing the Service Release
Note: If you installed the Service Release without performing the above procedure, see the workaround described in known issue Existing Projects Not Visible in Navigator, defect ID 235757.
Once the Service Release is installed, use the following procedure to add your project set to the XDE-ClearCase view-associated workspace.
To reload your project set after installing the Service Release
Project sets are a good way to ensure that teams of developers work on the correct set of related projects. When project files are placed under source control, they can be shared among users. Any new workspace can be populated with the same set of projects by using the Add Project Set to Workspace command.
With this Service Release, XDE performs a check upon startup to determine whether you are using ClearCase as your source control provider, and whether ClearCase has been configured to use the XDE compare/merge function as the Type Manager for XDE model files. If this configuration is needed, you are prompted to install the ClearCase XDE Type Manager.
If ClearCase is reinstalled or a new VOB is added, then the ClearCase XDE Type
Manager installer must be run again. However, before you can run the installer
on the same machine again, you must first uninstall the ClearCase XDE Type Manager,
and then reinstall it. As an alternative to uninstalling and reinstalling the
ClearCase XDE Type Manager installer, you can choose to run the underlying script
at:
<ClearCase-install-directory>\etc\utils\install_xde_eltype.bat.
Upon startup XDE may display errors that require running the XDE ClearCase Type Manager installer.
XDE info missing from VOB '<vob-tag>'. Please have the VOB owner run the XDE_CC Type Manager installer in VOB OBJECTS mode. You cannot proceed until this has been done.
The installer that is referenced in this message can be found at:
<xde-root>\RosePkg\fsk\Tools\cc_xde type manager installer\setup.exe
where <xde-root> is typically C:\Program Files\Rational\XDE.
XDE info missing from ClearCase default.magic file. Exiting.
When this occurs, please run the installer at:
<xde-root>\RosePkg\fsk\Tools\cc_xde type manager installer\setup.exe
and select Client mode. This will correct the condition.
For users of Rational XDE Modeler v2002 integrated with Rational ClearCase, creating an initial registered location before starting XDE will improve configuration of your development environment.
When starting Rational XDE from a shortcut, you should be aware of the following issues:
Files are considered "hijacked" when they are in a ClearCase snapshot view and have been made editable without being checked out. In some cases, it is customary to check out the required files before disconnecting from ClearCase; however, it is not always possible to determine all the files that are required. Hijacked files are the solution to this problem. When a file is required that has not been checked out, operation systems or IDE tools can be used to make the file editable. When the ClearCase connection is re-established, these hijacked files can be converted into checked-out files.
It is recommended that you check out only the files that you need. If new files need to be modified, you will need to hijack them when disconnected. Prior to reconnecting, make sure that all your XDE models are closed and XDE is closed. You can reconnect to the ClearCase server using the appropriate method for your edition. Once you are reconnected, it is important to update your view in order to convert any hijacked files to checked out files. Then restart XDE and reopen your models.
Use the following general procedure to perform a UCM delivery when using hijacked files.
Some teams that use Integrated Use Case Management (IUCM) can improve their multi-user compatibility by establishing a PathMap for both RequisitePro projects and XDE models. Consider following this guideline if your team uses IUCM with Rational RequisitePro and Rational XDE, and also meet any of the following criteria:
If your team is a candidate for establishing a PathMap for RequisitePro projects and XDE models, see the information about establishing a PathMap in the Integrated Use Case Management online Help.
Note: Rational ClearCase UCM users should be aware that, typically, you do not need to invoke the RequisitePro-XDE integration from your Integration view, only from your Development view. However, if you must invoke the integration from your Integration view, then you will need to manually update your PathMap to accurately reflect the location of the model you want to work with in your Integration view. Additionally, note that the Help is inaccurate when it states that the PathMap topic applies only to Rational Rose. In fact, PathMaps are also used for the RequisitePro-XDE integration.
The following table is a summary of defects fixed in this Service Release. For more details, click a category or defect ID.
| Category |
ID |
Summary |
| Action sequencer problem introduced |
||
| Triggered compare/merge session hangs Rational XDE |
||
| Compare/Merge performance improvements for multiple units |
||
| Some RTE Tag Value Sets not generated in the merged model |
||
| Saving merged model crashes Rational XDE |
||
| Incorrect order of added elements |
||
| Subunit directories left checked out |
||
| XDE Source Control preference can result in data loss | ||
| XDE Source Control Preferences: Auto-connect to ClearCase by Default | ||
| XDE-ClearCase Composite Unit Operations Support | ||
| Multibyte Characters Displayed Incorrectly in Set Activity ID Dialog Box |
||
| Updating a Model Does Not Bring in Any New Files/Folders | ||
| IBM WebSphere Certification Issue |
||
| Internationalization | RCSI Change Required for XDE 1.1 - I | |
| Java Validation Does Not Report Parameters with Empty Names as a Semantic Error |
||
| Rename EJB Updates All TypeExpressions That Use the Primary Key Type |
||
| Deployment Descriptor IDs Generated in IBM WSS AD Integration Are Not Unique |
||
| WebLogic Application Server 7.0 Support | ||
| General XDE | Storage Unit Reference Repair Is Broken |
|
| Elements disappear from the Model Explorer on undo checkout. |
||
| Package does not expand when there is a zero-length unit. |
||
| Find: Modeler error when finding elements on the drawing surface with unresolved note. |
The following table provides more details about the defects fixed in this Service Release.
| Category |
ID |
Description |
|
|
Action Sequencer Problem IntroducedApplies To: Users of Professional and Modeler editions of Rational XDE v2002 who installed an earlier hotfix released as ratlc000365915_msmrgeng.zip. A model with the following example configuration exists: Mode The model is changed to the following configuration: Mode If a compare and/or merge of the two models is attempted, Class1 will not be added to the merged model because Compare/Merge does not recognize that the move of Class1 occurred before its previous package was deleted. With this Service Release, Class1 will be added properly to the merged model. |
|
Triggered Compare/Merge Session HangsApplies To: Users of Professional and Modeler editions of Rational XDE v2002, including Modeler for IBM WSS AD. PreconditionThe user initiates a configuration management operation within Rational XDE that triggers a graphical merge. The description in the reproduction steps below is just one way to reach such a state. Steps to Reproduce the Problem
Common SymptomsThe graphical merge is initiated, the Compare/Merge session starts, the Compare/Merge perspective is presented, the busy cursor does not go away, and CPU usage is at 0%. It appears as if Rational XDE has hung. SolutionAfter installing the Service Release, triggered Compare/Merge sessions will no longer result in a deadlock situation because a different XDE session will be used to perform the triggered merge. Note that the original XDE session that issued the configuration management command that triggered the merge session will continue to block until the merge session has completed. This is normal and expected behavior since the original XDE session is simply waiting for the configuration management command to complete. NotesWith large models, Compare/Merge can take some time to initialize the session. The CPU usage distinguishes this normal operation from the hanging behavior. In the normal case, the CPU usage will be high whereas, if the session has hung, the CPU usage by the Compare/Merge session will essentially be zero. To avoid deadlocking the XDE session, the solution to this problem ensures that a new Rational XDE session is launched when a checkin command initiated in XDE results in a merge. The triggered Compare/Merge session takes place inside this new Rational XDE session. At the end of the triggered Compare/Merge session, the user should, as usual, either save the model and commit the merge session, or cancel the merge session. The Rational XDE session launched for the Compare/Merge session will automatically be shut down and no work other than the merge session should be performed in that XDE session. The original Rational XDE session from which the user triggered the graphical merge session (i.e. where the user performed the checkin operation) will be locked until the launched Compare/Merge session is either cancelled or committed. Once the user has completed the operation(s) that triggered the merge, they should return to the original Rational XDE session to proceed with further work. If you find that issuing a ClearCase checkin operation often results in the merge of many model units then you may wish to issue such commands from the Rational ClearCase Explorer. This can improve performance since the one XDE session already active will be reused for each merge session. |
||
Compare/Merge Performance Improvements for Multiple UnitsApplies To: Users of Rational XDE Professional v2002. Merge sessions involving a large model with a large number of subunit files take an inordinate amount of time to complete. With this Service Release, the time taken is greatly reduced. |
||
Some RTE Tag Value Sets Not Generated in the Merged ModelApplies To: Users of Professional and Modeler editions of Rational XDE v2002. When starting a merge session on Java models or C# models, some RTE Tagged Value Sets (e.g. “Merge”) will not be generated in the merged model. These Tagged Value Sets are used by the language add-ins while generating the code from the merged model. This Service Release restores the generation of the missing Tagged Value Sets. |
||
Saving Merged Model Crashes Rational XDEApplies To: Users of Professional and Modeler editions of Rational XDE v2002. |
||
Incorrect Order of Added ElementsApplies To: Users of Professional and Moderler editions of Rational XDE v2002. A model with the following example configuration exists: Model Model In the example used in the above use case, Parameter1 and Parameter2 are deleted and ParameterA, ParameterB, and ParameterC are added as expected. However, the order of the parameters added is not preserved and ParameterB and ParameterC are stored in reverse order. In general, this defect will manifest itself when one or more elements in a collection (classes in a package, operations in a class, etc.) have been deleted in one Compare/Merge contributor, and more than one element has been added at the same location, unless other rules (such as parameter name matching) are in effect. Although the order of the parameters is incorrect, no data is lost. With this Service Release, the order of the newly added parameters will be preserved in merge sessions.
|
||
|
|
Subunit Directories Left Checked OutApplies To: Users of Professional and Modeler editions of Rational XDE v2002 who use the ClearCase Plugin v1.3.0 with XDE. Steps to Reproduce the Problem
This Service Release will ensure that the parent directory of a newly added model subunit does not appear in the list of units to be added to source control and, therefore, the user will not be able to choose to keep the directory checked out. The directory will be added to source control and will be checked in. |
|
XDE Source Control Preference Can Result in Data LossApplies To: Users of Rational XDE Professional v2002: Java Platform Edition. If you allow in-memory edits and also allow XDE to do nothing when checked-in files are saved, then the edits are lost without warning when exiting XDE. SolutionThe Allow checked in files to be edited check box and the When checked in files are saved box are removed to prevent this problem. You must check out the files (or allow XDE to check out the files through the When checked in files are edited preference) before editing. |
||
XDE Source Control Preferences: Auto-connect to ClearCase by DefaultApplies To: User of Rational XDE Professional v2002: Java Platform Edition. Configuration management operations are not available by default as XDE starts, without starting the ClearCase integration. SolutionThe Service Release changes the default for the Automatically connect to source control provider at startup preference from disabled to enabled. You can access this preference by clicking Windows > Preferences, expanding Rational XDE, and clicking Source Control. |
||
XDE-ClearCase Composite Unit Operations SupportApplies To: Users of Professional and Modeler editions of Rational XDE v2002. Changes to the model that resulted in multiple, related control units being checked out, but only part of the model was checked in, encountered errors when loading the model in a second view. In a single development stream, checking in partial models results in other users seeing partial changes leading to model corruption. This can also occur in private streams if changes are delivered piecemeal to a shared (integration) stream. Steps to Reproduce the ProblemThe user will have made changes to the model that resulted in multiple, related control units being checked out.
Common SymptomsErrors are seen when loading the model in a second view. The model may not load under certain circumstances. Changes are lost. SolutionThis Service Release adds functionality to help ensure the model is placed under ClearCase control in a consistent manner. When working with Rational XDE Professional v2002: Java Platform Edition, you receive “augmented” file lists when doing a check in, add to source control, or update operation. This dialog box contains not only the file(s) you selected, but also files that XDE determines are required to maintain model consistency. You should confirm the operation on all the files to ensure consistency in ClearCase. For more information, see Composite Object Versioning Support. |
||
Multibyte Characters Displayed Incorrectly in Set Activity ID Dialog BoxApplies To: Users of Professional and Modeler editions of Rational XDE v2002 who use the ClearCase Plugin v1.3.0 with XDE. Steps to Reproduce the Problem
You will see incorrect characters in the pull-down activity menu.SolutionThis Service Release ensures that multibyte characters are displayed correctly. |
||
Updating a Model Does Not Bring in Any New Files/FoldersApplies To: Users of Professional and Modeler editions of Rational XDE v2002. Updating, or getting the latest version of an XDE model element only updates the control unit of the selected element . This results in inconsistent models in memory and broken links to items that should be present or <<Fail to get name>> instead of a model element name. SolutionThe new composite object versioning (COV) functionality ensures that not only the model, but its associated folder are affected by an update or get latest version operation. In the case of the associated folder, the update is done recursively. The model then reloads to bring in all the new elements. This ensures that the model is consistent both under source control and in memory.
|
||
IBM WebSphere Certification IssueApplies To: Users of Professional and Modeler editions of Rational XDE v2002, including Modeler for IBM WSS AD. BackgroundNeither IBM WebSphere Workbench nor IBM WebSphere Studio Application Developer notifies Rational XDE when a file is deleted in the Navigator view until after the processing of the file removal from the project. XDE is unable to offer any formal recovery because the file is already deleted by the time XDE is notified. If there are unsaved edits in editors associated with the file being deleted, these unsaved edits will be lost. An example of this scenario is when deleting a model file from the Navigator when an editor associated with the model is open and contains unsaved edits. Steps to Reproduce the Problem
Common SymptomsAfter deleting components of a project in the IBM WebSphere Shell Navigator View, components of the XDE model also disappear. SolutionThis Service Release fixes the issue. After this Service Release is installed, deleting a file associated with a model that has an open editor with unsaved edits will bring up a notification dialog box. Previous to this fix, no dialog box was presented. The dialog box states: "The file has been deleted. Your changes will be lost." |
||
RCSI Change Required for XDE 1.1 - IApplies To: Users of Professional and Modeler editions of Rational XDE v2002. Online Help available in English only. SolutionWith this Service Release, the Japanese-language XDE Help home root-level topic is opened when the system locale setting is Japanese. |
||
|
|
Java Validation Does Not Report Parameters with Empty Names as a Semantic ErrorApplies To: Users of Rational XDE Professional v2002: Java Platform Edition. If model validation or code generation is attempted on a Java code model that contains an operation with a non-return parameter with an empty name, an exception is thrown that prevents successful completion of semantic validation. Steps to Reproduce the Problem
An Unspecified Error dialog box appears. If validation is invoked through code generation, validation ends and parameters with empty names are generated in the code. This code will not compile. SolutionThis Service Release fixes the issue. Once the Service Release has been installed, the semantic checker for Java will add an error to the task window whenever a parameter with an empty name is detected during validation. In the event that semantic checking fails for unanticipated reasons prior to code generation, the message "Failure during model validation. Operation aborted" appears in the output window and code will not be generated. |
|
| J2EE | Rename EJB Updates All TypeExpressions That Use the Primary Key TypeApplies To: Users of Rational XDE Professional v2002: Java Platform Edition who use the XDE EJB rename feature to rename Entity beans. Precondition and BackgroundThe XDE EJB rename feature responds to a rename of an EJB by renaming many parts of the EJB. The rename causes the classes and interfaces to be named based on the naming preferences specified on the Rational XDE, Java, EJB/Servlet page of the Preferences dialog box. In the case of an entity bean, this will also rename the primary key class. This primary key class is used for parameter and return types in the bean. The rename will change all of the places this primary key class is used. This defect updates usages of the primary key type. If the type of the primary key is used for more than just the primary key, some TypeExpressions will be updated in error. A common problem will be when the primary key type is a library class (such as java.lang.String) rather than a bean-specific class (such as myBeanPrimaryKey). This will occur when a primary key field is used for the primary key of the Entity bean. Steps to Reproduce the Problem
As a result, the usage to java.lang.String is renamed to TestPrimaryKey and the TypeExpression for the CMP field becomes TestPrimaryKey. Several TypeExpressions may be affected based on how many have used the same type as the previous primary key value. The expected result is for the feature to recognize that the bean is using a simple key and not rename all usages that are the same as the primary key type. Common SymptomsAfter a rename, several compile errors are introduced in the Entity bean. One or more attributes and methods have to be repaired. SolutionThis Service Release fixes the issue. |
|
Deployment Descriptor IDs Generated in IBM WSS AD Integration Are Not UniqueApplies To: Users of Rational XDE Professional v2002: Java Platform Edition installed into an existing IBM WebSphere Studio Application Developer installation who have installed and use WSS AD and XDE EJB features. BackgroundThe XDE to WSS AD integration for EJBs is implemented through the EJB deployment descriptor file. Some of the elements in the file will have an “id=” with a string inside the element tag. In the EJB deployment descriptor DTD, this is described as follows: The ID mechanism is to allow tools that produce additional deployment information (i.e., information beyond the standard EJB deployment descriptor information) to store the non-standard information in a separate file, and easily refer from these tools-specific files to the information in the standard deployment descriptor. WebSphere uses this as described above to integrate its various deployment descriptors. IBM WSS AD features only introduce these IDs as needed; for instance, when the EJB Entity Bean to database mapping is generated. XDE outputs the IDs every time the Update WSS AD From XDE command is carried out. The defect can cause the IDs to be output incorrectly every time WSS AD is updated using the integration command. Steps to Reproduce the ProblemUsing XDE integrated with WSS AD:
The resulting error message mentions non-uniqueness of IDs for CMP fields. In the EJB deployment descriptor, the IDs will not be unique. The expected result is that the IDs have been generated by XDE and should be to the format required by IBM WSS AD. In this case, they should have been unique. Common SymptomsIf these IDs are not unique, then WSS AD reports the error in the task window. WSS AD will need these IDs fixed to be unique in order to deploy from their dialog boxes. SolutionThis Service Release fixes the issue. |
||
WebLogic Application Server 7.0 SupportApplies to: Users of Rational XDE Professional v2002. XDE supports deployment of J2EE applications to several application servers. This Service Release adds support for deployment to WebLogic Application Server version 7.0. After this fix has been applied, when you invoke J2EE deployment, the deployment wizard offers you the option to deploy to WebLogic Application Server version 7.0, in addition to the previously supported servers. The subsequent wizard pages behave in the same manner and request the same types of information as in the v2002 wizard. |
||
Storage Unit Reference Repair Is BrokenApplies To: Users of Professional and Modeler editions of Rational XDEl v2002 who work on models under source control and create new files (separate units) in shared containers such as packages.Steps to Reproduce the Problem
The subunit file for the package on user 2’s machine contains a reference to a missing subunit file. A defect causes a zero-length file to be created with the name of the missing subunit (class1.clx). The presence of the zero-length file disables the GUI indication that a subunit is missing (a red cross in the Model Explorer). It also causes the Model Explorer to fail to display all children in the container (RATLC00230720, RATLC00230672). Common SymptomsValidation of a model fails with a hard error indicating a “failure to parse” zero-length files in the model. SolutionThis Service Release fixes the issue. |
||
Elements Disappear from the Model Explorer on Undo CheckoutApplies To: Users of Professional and Modeler editions of Rational XDE v2002. When making separate units within a model and adding them to source control, sometimes undoing the checkout of an element that hasn't changed causes elements to disappear from the Model Explorer. In this Service Release, the model element no longer disappears. |
||
|
|
Copy and Paste Breaks Element ReferencesPreviously, when copying a collaboration from one model to another, references from some of the elements in the collaboration to elements outside the collaboration were broken. For example, the reference from an object or classifier role in a collaboration to the classifier of which it was an instance was not preserved when performing a cross-model paste. Solution This has been fixed and the references now refer back to the elements in the original model after a cross-model paste (assuming they were not included in the set of elements pasted, in which case the references point to the pasted elements). |
|
Package Does Not Expand When There Is a Zero-Length UnitApplies To: Users of Professional and Modeler editions of Rational XDE v2002 who have zero-length subunit files in a model (RATLC00046296, RATLC00230617). Steps to Reproduce the Problem
All elements added to the package after the zero-length subunit is introduced do not appear in the Model Explorer when the package is expanded. This Service Release fixes the issue. |
||
Printing Diagrams on a Single PageUnable to satisfactoraly print a diagram on letter-size paper that was set up to print on plotter paper. SolutionRational XDE now allows you to "fit to page," so you can print the diagram to a single page, regardless of the paper size. |
||
Moving Sequence Diagram Components in Zoom-Out Magnification Causes Data Corruption of DiagramApplies To: Users of Professional and Modeler editions of Rational XDE v2002. If you open a sequence diagram, zoom out, then move lifelines, the diagram is corrupted. With this Service Release, you can make modifications in the zoomed out state. XDE verifies that all lifelines are selected before extending lifelines or bumping messages to prevent diagram corruption. |
||
Error on Saving Updated Subunits When Parent Is UnchangedWhen attempting to save updates to subunits within a model, an error
was sometimes encountered if the Subunits are now saved without error when the parent unit is read-only and does not need to be saved. |
||
Rose Diagrams Appear Distorted When Imported to XDEAll diagrams created in Rose have to be modified because auto-resize is turned off on all imported diagram elements in XDE. SolutionImporting Rose diagrams in XDE now behaves correctly. If AutoSize is turned on in Rose, XDE correctly enables auto-resizing after the import. |
||
Find: Modeler Error When Finding Elements on the Drawing Surface with Unresolved NoteApplies To: Users of Professional and Modeler editions of Rational XDE v2002. If the user has any note or text in his/her search space with a broken reference, XDE’s find command will return no search results. Steps to Reproduce the Problem
Result: Nothing is found. SolutionThis Service Release resolves this issue. |
The following table is a summary of known issues in this Service Release. For more details, click a category or defect ID.
| Category |
ID |
Summary |
| Rational XDE Patterns Can Be Corrupted During Merge | ||
| Rational XDE Code Templates Can Be Corrupted During Merge | ||
| Potential Data Loss When Separate Subunits Made Under CM Control | ||
| Failure to Combine Separate Units During a Merge Involving ClearCase | ||
| Existing Projects Not Visible in Navigator | ||
| Get "Failed to get name" When Opening Model That Was Not Updated | ||
| Composite Object Versioning (COV) Does Not Cross Model Boundaries | ||
| XDE Does Not Return Dependent CM Units When Model Is Closed | ||
| ClearCase Views Missing from Views List on XDE Startup | ||
| ClearCase Plugin Does Not Save Files Before Moving a Project into a View | ||
| Rebase with an Open Model Fails to Reload | ||
| File Extensions Appear in Configuration Management Dialog Boxes for Subunits Not Selected in the Model Explorer | ||
| ClearCase Menu in XDE Fails to Appear When Installing XDE First, Then ClearCase | ||
| Incorrect Configuration Management Status After Model Update | ||
| Internationalization Support in XDE Startup and XDE ClearCase Installer | ||
| Error Upon Importing XDE Model When XDE Launched in J2EE Perspective | ||
| Obsolete Documentation for Adding Template Arguments for Template Parameters |
The following table provides more details about the known issues in this Service Release.
|
Category |
ID |
Description |
Rational XDE Patterns Can Be Corrupted During MergeRational XDE stores pattern-processing instructions as properties (tagged values) of model elements; for instance, the location where the results of a pattern expansion should be placed is called it’s “expansion location” and that location is determined by a set of properties that includes ExpansionLocationType and ExpansionLocationContextElement. Choices for the type can be Context or Argument, which indicate (respectively) that the expansion location is some specific model element or that the location is determined (indirectly) by one of the template argument values supplied to the pattern at expansion time. To make the pattern consistent (and expandable), the value stored in ExpansionLocationContextElement must be either a reference to a particular element in the target model or a reference to one of the pattern’s template parameters, depending on the value of the ExpansionLocationType property. If the pair of properties has inconsistent values (e.g., type says Context but the context element value is a template parameter of the pattern), then the pattern won’t expand correctly. A common symptom of this problem is to see errors when trying to apply a pattern following a merge. Steps to Reproduce the Problem
SolutionWhen merging patterns, the recommended approach is to consistently choose all properties of a pattern from the same contributor. |
||
Rational XDE Code Templates Can Be Corrupted During MergeApplies To: Users of Professional and Modeler editions of Rational XDE v2002. Rational XDE stores code templates as a set of properties (tagged values); for instance, Template1Body stores the text of the code template and Template1ParameterValueReferences stores references to the argument values used to replace the parameterized pieces of the text. The text property is dependent on the argument value property — if every parameter appearing in the text doesn’t have an argument supplied for it, then the code template won’t expand correctly. During a CM merge operation, it is possible for a user to choose properties from different contributors such that these dependencies between the properties are violated. A common symptom of this problem is to see errors when trying to expand the code template following a merge. Steps to Reproduce the Problem
SolutionWhen merging code templates, the recommended approach is to consistently choose all properties of a code template from the same contributor. |
||
Potential Data Loss When Separate Subunits Made Under CM ControlApplies To: Users of Professional and Modeler editions of Rational XDE v2002. When combining or separating model units, you should ensure no one else is working on the same units. Otherwise, you can run into scenarios like the following:
Since the separation of package P from model M is applied automatically during the merge, no visible merge session is needed and the merge occurs silently. However, should there be conflicts for other reasons, then a merge session will be presented to the user. At that point, the user will be able to reverse the automatic application of the separation of package P from model M. However, this would result in the loss of the separated version of package P. |
||
Failure to Combine Separate Units During a Merge Involving ClearCaseCompare/Merge can silently fail to combine a unit during a merge. For example, consider the following scenario:
Note that this defect applies to UCM rebase operations as well, and also applies even if UCM isn't used and simple check-ins trigger merges. When user 2 delivers, ClearCase sees that both contributors have modified M.mdx and so the type manager for XDE models is invoked to perform the merge silently. XDE Compare/Merge is invoked. However, the result of the merge passed back to ClearCase will not have package P combined with model M—it will remain a separate unit. There is no warning or other indication of this failure to combine the units. Even when the merge isn't silent, this will occur. For example, consider the following scenario:
When user 2 delivers, ClearCase sees that both contributors have modified M.mdx and so the type manager for XDE models is invoked to perform the merge silently. XDE Compare/Merge is invoked. However, XDE Compare/Merge detects that there is a conflict in the renaming of diagram D and so the silent merge fails. ClearCase then invokes the type manager for XDE models to resolve the conflict via the user. Consequently, an XDE Compare/Merge session is presented to the user. The user will see a conflict regarding the name of the diagram. The user will also see that the merged model indicates <failed to get unit> for the package P, which is normal for a ClearCase-initiated merge since the P.pkx unit isn't accessible during the merge of M.mdx. The package P will have a delta on it. Clicking on the package will show that the delta is for the name of the package's storage unit. In the merged model, the name is combined with the model and the other contributors show P as a separate unit. However, in the saved merged model, P erroneously remains a separate unit. WorkaroundsTo work around this issue, combining of units needs to occur in such a way that the resulting merge will be trivial--that is, the version of the M.mdx file being delivered is the immediate successor to the version in the integration stream. One way to achieve this is to do the following:
This procedure is sure to work. However, it isn't necessary if you practice strong ownership of the type of parent unit into which the subunit is being combined. In this case, the parent unit is the root model file itself. However, in many cases it will be a package that might be "owned" by a particular developer who knows that nobody else is working on it. Then, the combining of the unit can proceed without the full procedure above. Note that it isn't sufficient to simply succeed in the delivery—if others have the older versions of the model with P still a separate unit, then their rebase will result in a merge that leaves P as a separate unit. The procedure just above avoids this. If you aren't using UCM, then you simply need to ensure that the merge
is trivial. Typically, this occurs when you check out a file and no
one else has subsequently checked in any changes before you check in
your changes. Furthermore, to avoid potential data loss, it's best that
no one even have the file checked out. For example, suppose you successfully
combine the unit because no one checked in a change to M.mdx between
the time you checked it out and checked it back in. If someone had checked
out the unit before you checked in your changes, then that person still
has package P as a separate unit. However, any changes to P as a separate
unit will be ignored since the model now has P combined into M.mdx—the
separate P.pkx file is no longer part of the model. |
||
| Configuration Management | Existing Projects Not Visible in NavigatorWhen starting Rational XDE and selecting the view where your project set files were stored, you see a message similar to the following:
However, when startup completes, your existing project files do not appear in the Navigator. Note: To avoid this issue, save your project set before installing the Service Release, as explained in Pre- and Post-Installation Procedures for Migrating Your Default Workspace, in the section Restrictions and Guidelines on Using this Service Release. Solution Your workaround depends on whether or not you have been working in the default workspace.
Use this procedure to migrate files from your previous default workspace to the new workspace. To populate the new workspace with your existing project set (default workspace)
Use this procedure to migrate files from your previous non-default workspace to the new workspace. Alternatively, you can choose to continue using your previous workspace by running xde.exe directly or using a shortcut to it, instead of using the XDE-created shortcut. To populate the new workspace with your existing project set (non-default workspace)
|
|
Get "Failed to get name" When Opening Model That Was Not UpdatedApplies To: Users of Rational XDE Professional v2002: Java Platform Edition who are using Rational ClearCase on a single stream. When performing a merge of a model, a new version of a package file may be brought in that contains references to files not yet on disk because the folder was not updated. The “Failed to get name” indication would also be shown in this case. Steps to Reproduce the ProblemThe following scenario assumes that you have two users (user1 and user2) working on a single development stream in their own, separate views. The following scenario assumes that you have two users (user1 and user2) working on a single development stream in their own, separate views.
Common SymptomsNew elements that have been added to a package in the first view have “Failed to get name” as their displayed name. SolutionWhen you encounter this situation, it is recommended that you close your XDE model, ensuring that nothing is saved to disk or in source control. Once this is done, execute the ClearCase Update view command to bring in all changes from this other view. The model will load correctly after this is done. |
||
Composite Object Versioning (COV) Does Not Cross Model BoundariesApplies To: Users of Professional and Modeler editions of Rational XDE v2002. BackgroundThe new composite object versioning (COV) functionality provided in this Service Release only covers related model elements in a single model. Related model elements between models will not be listed by the COV dialog boxes. This may result in inconsistencies between models. Steps to Reproduce the Problem
Solution When working with multiple, related models, you must do the CM operation
at least once in each model to ensure consistency. |
||
XDE Does Not Return Dependent CM Units When Model Is ClosedApplies To: Users of Professional and Modeler editions of Rational XDE v2002. Steps to Reproduce the Problem
SolutionPerform all CM operations on XDE model elements from within the XDE Model Explorer. Enhanced functionality has been added to perform composite unit operations within an XDE model (see release note for RATLC00046732). However, this functionality is only available on models that are open. |
||
ClearCase Views Missing from Views List on XDE StartupApplies To: Users of Professional and Modeler editions of Rational XDE Professional v2002 who are also using ClearCase. Upon startup, XDE presents a list of ClearCase views available on your
local workstation. Sometimes, views are missing from this list because
the views path is not included in the following key: SolutionOne workaround is to manually enter the path to the missing view in the above Workspace key. Another workaround is to open ClearCase Explorer, click the View tab, and determine if any shortcuts are broken. Broken view shortcuts will correspond to the missing views. Fix the shortcut by removing it, then adding it again. Upon refreshing the registry, the view will appear in the Workspace key, and the view will show up in the list of views the next time you starting. |
||
ClearCase Plugin Does Not Save Files Before Moving a Project into a ViewApplies To: Users of Rational XDE Professional v2002: Java Platform Edition who use Rational ClearCase in conjunction with XDE. You can create projects and model files in your own local workspace area before deciding to move them under source control. With ClearCase, this adds an extra step of physically moving the files into a directory under a view. Steps to Reproduce the Problem
Common SymptomsA model is empty or controlled units are missing after moving the parent project into ClearCase. SolutionYou should ensure that your model is saved and closed before moving a project into ClearCase. |
||
|
|
Rebase with an Open Model Fails to ReloadApplies To: Users of Professional and Modeler editions of Rational XDE v2002 who use Rational ClearCase in conjunction with XDE. Expected model changes will not appear after a rebase operation if the rebase is performed while Rational XDE models are open. Part of the Rational ClearCase UCM process mandates that users rebase their development stream in order to get updated artifacts from the latest project baseline. This rebase operation is typically conducted in parallel to, and often outside of, the usage of the integrated development environment (IDE). This may result in changes not being automatically apparent in the IDE. Steps to Reproduce the Problem
SolutionWhenever running the Rational ClearCase UCM rebase operation, first close any open Rational XDE models. It is not necessary to close the IDE. Reopening the model after the rebase operation has completed will show all the changes. |
|
File Extensions Appear in Configuration Management Dialog Boxes for Subunits Not Selected in the Model ExplorerApplies To: Users of Professional and Modeler editions of Rational XDE v2002 who use Rational ClearCase in conjunction with XDE. Subunits that you have not selected may appear in configuration management dialog boxes with unexpected file extensions. Steps to Reproduce the Problem
SolutionXDE uses a default logical name, which is the file name, for units that have not been called. You can safely ignore these files. |
||
ClearCase Menu in XDE Fails to Appear When Installing XDE First, Then ClearCaseApplies To: Users of Rational XDE Professional v2002: Java Platform Edition who use Rational ClearCase in conjunction with XDE. Even when both Rational XDE and ClearCase are installed, the ClearCase menu will not appear in XDE if the products are installed out of order. Upon installation, Rational XDE Professional v2002: Java Platform Edition
determines whether Rational PreconditionThe installation is performed on a workstation where no Rational products have been installed. Steps to Reproduce the Problem
SolutionThe avoid this issue, ensure that ClearCase is installed prior to installing
Rational XDE. This will allow If this is not possible, use the following procedure to enable ClearCase integration:
You may need to add the ClearCase command set to your perspective(s) at this point. To do so:
|
||
Incorrect Configuration Management Status After Model UpdateThe Configuration Management status becomes incorrect in certain situations while using XDE and ClearCase, after issuing an update to the model. A symptom of this is that you cannot rename classes in the Model Explorer. SolutionTo work around this problem, close and reopen your model after doing an update on the view. |
||
Internationalization Support in XDE Startup and XDE ClearCase InstallerComponents of this Service Release will fail on 16-bit character operating systems if 16-bit characters are part of pathnames to ClearCase view root and VOB directories. For example, on a Japanese operating system, if these paths contain Kanjii (16-bit) characters, XDE startup and the XDE ClearCase Type Manager installer will not function; however, if these paths are restricted to 8-bit Latin characters, they will operate correctly running on a Japanese operating system. |
||
Error Upon Importing XDE Model When XDE Launched in J2EE PerspectiveApplies To: Users of Rational XDE Professional v2002: Java Platform Edition. If the Modeling perspective was not loaded in WebSphere Application Developer when you try to import an XDE model to an existing project (for example, a Java project), you may see an error message and import model will fail. Steps to Reproduce the Problem:
Solution
|
||
Obsolete Documentation for Adding Template Arguments for Template ParametersThe Help topic "Adding Template Arguments for Template Parameters" includes obsolete procedures. SolutionThe updated procedures are provided below: To add a template argument for a model element template parameter
To add a template argument for a data type template parameter
|
If you have questions about installing, using, or maintaining this product, contact Rational Customer Support as follows:
| Your Location | Telephone | Facsimile | |
| North America |
(800) 433-5444 (408) 863-4000 |
(781) 676-2460 |
support@rational.com |
| Europe, Middle East, Africa |
+ 31 (0) 20 4546 200 |
+31 (0) 20-4545-201 |
support@europe.rational.com |
| Asia Pacific |
+61-2-9419-0111 |
+61-2-9419-0123 |
support@apac.rational.com |
When you contact Rational Customer Support, please be prepared to supply the following information:
Rational, Rational Software Corporation, Rational the e-development company, Rational Developer Network, ClearCase, ClearCase Attache, ClearCase MultiSite, ClearDDTS, ClearQuest, ClearQuest MultiSite, DDTS, Object Testing, Object-Oriented Recording, ObjecTime & Design, Objectory, PerformanceStudio, Rational ProjectConsole, PureCoverage, PureDDTS, PureLink, Purify, Purify'd, Quantify, Rational Apex, Rational CRC, Rational Rose, Rational Suite, Rational Summit, Rational Visual Test, Requisite, RequisitePro, RUP, SiteCheck, SoDA, TestFactory, TestFoundation, TestMate, The Rational Watch, AnalystStudio, ClearGuide, ClearTrack, Connexis, e-Development Accelerators, ObjecTime, Rational Dashboard, Rational PerformanceArchitect, Rational Process Workbench, Rational Suite AnalystStudio, Rational Suite ContentStudio, Rational Suite Enterprise, Rational Suite ManagerStudio, Rational Unified Process, XDE, SiteLoad, TestStudio, VADS, among others, are either trademarks or registered trademarks of Rational Software Corporation in the United States and/or in other countries. All other names are used for identification purposes only, and are trademarks or registered trademarks of their respective companies.
Microsoft, the Microsoft logo, Active Accessibility, Active Client, Active Desktop, Active Directory, ActiveMovie, Active Platform, ActiveStore, ActiveSync, ActiveX, Ask Maxwell, Authenticode, AutoSum, BackOffice, the BackOffice logo, bCentral, BizTalk, Bookshelf, ClearType, CodeView, DataTips, Developer Studio, Direct3D, DirectAnimation, DirectDraw, DirectInput, DirectX, DirectXJ, DoubleSpace, DriveSpace, FrontPage, Funstone, Genuine Microsoft Products logo, IntelliEye, the IntelliEye logo, IntelliMirror, IntelliSense, J/Direct, JScript, LineShare, Liquid Motion, Mapbase, MapManager, MapPoint, MapVision, Microsoft Agent logo, the Microsoft eMbedded Visual Tools logo, the Microsoft Internet Explorer logo, the Microsoft Office Compatible logo, Microsoft Press, the Microsoft Press logo, Microsoft QuickBasic, MS-DOS, MSDN, NetMeeting, NetShow, the Office logo, Outlook, PhotoDraw, PivotChart, PivotTable, PowerPoint, QuickAssembler, QuickShelf, RelayOne, Rushmore, SharePoint, SourceSafe, TipWizard, V-Chat, VideoFlash, Virtual Basic, the Virtual Basic logo, Visual C++, Visual C#, Visual FoxPro, Visual InterDev, Visual J++, Visual SourceSafe, Visual Studio, the Visual Studio logo, Vizact, WebBot, WebPIP, Win32, Win32s, Win64, Windows, the Windows CE logo, the Windows logo, Windows NT, the Windows Start logo, and XENIX, among others, are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or in other countries.
Sun, Sun Microsystems, the Sun Logo, Ultra, AnswerBook 2, medialib, OpenBoot, Solaris, Java, Java 3D, ShowMe TV, SunForum, SunVTS, SunFDDI, StarOffice, and SunPCi, among others, are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries
VSFlexGrid Pro is a trademark of ComponentOne LLC,Copyright 2001.All rights reserved.
J-Integra is a trademark of Intrinsync Software, Inc.
Design Patterns: Elements of Reusable Object-Oriented Software, by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides. Copyright © 1995 by Addison-Wesley Publishing Company, Inc. All rights reserved.
Note that in the text below, "Program" refers to Rational® XDE™ software and associated documentation.
The Program is composed of multiple separately written and copyrighted modular software components. Some of the components are provided under separate, non-Rational licenses that permit copying, modification and redistribution of those components. Such components are licensed pursuant to the terms of the available license. The components and applicable license terms are set forth below.
This product is accompanied by software developed by the Eclipse Project (http://www.eclipse.org).
1. XML4J 3.2.1
The Program is accompanied by software based on Xerces 1.4.2 developed by The Apache Software Foundation as part of the Apache XML project. XML4J is located in XDE\hshell\plugins\org.apache.xerces\xerces.jar. Your use of XML4J in binary code form accompanying the Program is subject to the terms and conditions of the Apache Software License 1.1 from (http://xml.apache.org/LICENSE). More specifically:
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Source code for XML4J is available (http://www.alphaworks.ibm.com/tech/xml4j).
2. ANT 1.3
The Program is accompanied by software developed by The Apache Software Foundation as part of the Jakarta project. The ANT code included with the Program in plugins/org.eclipse.ant.core/ant.jar includes no modifications. Your use of ANT in binary code form accompanying the Program is subject to the terms and conditions of the Apache Software License 1.1 from (http://jakarta.apache.org/ant/manual/). More specifically:
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.4. The names "ANT" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
3. Rhino 1.5.1
The Program is accompanied by software developed by Mozilla as part of the Rhino project. The Rhino code included with the Program in plugins/org.eclipse.scripting/js.jar includes no modifications. Your use of Rhino in binary code form accompanying the Program is subject to the terms and conditions of the Netscape Public License 1.1 from (http://www.mozilla.org/MPL/NPL-1.1.html). The Rhino binary code included in the Program includes no modifications. Source code for the Rhino binaries is available at (http://www.mozilla.org/rhino/) under terms of the Netscape Public License 1.1.
4. The Java Ssh Applet
The Program is is accompanied by software developed by Cedric Gourio. The source code is located in XDE\hshell\plugins\org.eclipse.vcm.core.cvs.ssh\vcmcvssshsrc.zip. The binary code is located in XDE\hshell\plugins\org.eclipse.vcm.core.cvs.ssh\vcmcvsssh.jar. The Java Ssh Applet is:
Copyright © 1998 Cedric Gourio
(http://www.cl.cam.ac.uk/~fapp2/software/java-ssh/)
(javassh@france-mail.com)
The Sun J2EE Patterns Catalog from Sun's Java Center(sm) consulting organization is included in its entirety within this product. The Sun J2EE Patterns are used with permission from the book "Core J2EE Patterns" by Deepak Alur, John Crupi, and Danny Malks, published by Sun Microsystems Press/Prentice Hall. Copyright 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303. All rights reserved. SUN PROVIDES EACH J2EE PATTERN "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
This product includes VSFlexGrid software developed by ComponentOne LLC. VSFlexGrid Pro is a trademark of ComponentOne LLC,Copyright 2001.All rights reserved.
This product includes J-Integra software developed by Intrinsync Software Inc. J-Integra is a trademark of Intrinsync Software, Inc.
The Program is accompanied by software developed by Mozilla as part of the Rhino project. The Rhino code included with the Program in XDE\hshell\plugins\com.rational.hshell.ratltool\js.jar or XDE\JavaScriptPkg\js.jar includes modifications necessary to use the scripting engine with the Program. The source code corresponding to these modifications can be found in the directory "XDE\License Information\Rhino". Your use of Rhino in binary code form accompanying the Program is subject to the terms and conditions of the Netscape Public License Version 1.1 which is found at "XDE\License Information\Rhino\NetscapePublicLicense-1.1.html" and on the Internet at (http://www.mozilla.org/MPL/NPL-1.1.html). Source code for Rhino is available at (http://www.mozilla.org/rhino/) under the terms of the Netscape Public License 1.1.
The Program is accompanied by software developed by James Clark. The Expat code included with the Program includes minor modifications. The modifications can be found in the directory "XDE\License Information\Expat". Your use of Expat in binary code form accompanying the Program is subject to the terms and conditions of the Mozilla Public License 1.0 which is found at "XDE\License Information\Expat\MozillaPublicLicense-1.0.html" and on the Internet at (http://www.mozilla.org/MPL/MPL-1.0.html). Source code for Expat is available from (http://www.jclark.com/xml) under the terms of the Mozilla Public License.
The Program is accompanied by software developed by The Apache Software Foundation as part of the Apache XML project. The Xerces code included with the Program in XDE\hshell\plugins\org.apache.xerces\xerces.jar (or XDE\AddIns\common) includes no modifications. Your use of Xerces in binary code form accompanying the Program is subject to the terms and conditions of the Apache Software License 1.1 which is found at "XDE\License Information\Xalan-Xerces\ApacheSoftwareLicense-1.1.txt" and on the Internet at (http://xml.apache.org/LICENSE). Specifically, Xerces is:
* Copyright (c) 1999 The Apache Software Foundation. All rights * reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://www.apache.org/)." * Alternately, this acknowledgment may appear in the software itself, * if and wherever such third-party acknowledgments normally appear. * * 4. The names "Xerces" and "Apache Software Foundation" must * not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact apache@apache.org. * * 5. Products derived from this software may not be called "Apache", * nor may "Apache" appear in their name, without prior written * permission of the Apache Software Foundation.THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see (http://www.apache.org/.)
The Program is accompanied by software developed by Carnegie Mellon University. The mpack code included with the Program includes minor modifications. The source code corresponding to these modifications can be found in the directory "XDE\License Information\mpack". Your use of mpack in binary code form accompanying the Program is subject to the terms and conditions of the license that is found at "XDE\License Information\mpack\mpack_license.txt". Specifically, mpack is:
(C) Copyright 1993,1994 by Carnegie Mellon University All Rights Reserved. Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Carnegie Mellon University not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Carnegie Mellon University makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Portions of this software are derived from code written by Bell Communications Research, Inc. (Bellcore) and by RSA Data Security, Inc. and bear similar copyrights and disclaimers of warranty.
Portions of this product were created using LEADTOOLS (c)1991-1999, LEAD Technologies, Inc. ALL RIGHTS RESERVED.
This product includes Regex software developed by Dr. John Maddock Copyright (c) 1998-1999.
This product includes BasicScript © 1996-2001, Summit Software Company.
Portions covered by U.S. Patent Nos. 5,193,180 and 5,335,334 and 5,535,329 and 5,574,898 and 5,649,200 and 5,675,802 and 5,754,760 and 5,835,701 and 6,049,666 and 6,126,329 and 6,167,534 and 6,206,584. U.S. Patents Pending. International Patents Pending.
Purify is licensed under Sun Microsystems, Inc., U.S. Patent No. 5,404,499.
Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in the applicable Rational Software Corporation license agreement and as provided in DFARS 277.7202-1(a) and 277.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct. 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 227-14, as applicable.
This document and its associated software may be used as stated in the underlying license agreement. Rational Software Corporation expressly disclaims all other warranties, express or implied, with respect to the media and software product and its documentation, including without limitation, the warranties of merchantability or fitness for a particular purpose or arising from a course of dealing, usage, or trade practice.