IBM Rational Software Modeler Fix Pack 6.0.0.1 - Readme

For Rational Software Modeler, Version 6.0

To view the latest version of this file, see the readme at www3.software.ibm.com/ibmdl/pub/software/rationalsdp/rsm/60/html/readme_6001.html.

This file is available in the following national languages:

Brazilian Portuguese	Chinese - Simplified	Chinese - Traditional
French	German	Italian
Japanese	Korean	Spanish

Table of contents

1.0 About this release

IBM^® Rational^® Software Modeler Fix Pack 6.0.0.1 includes the fixes from all previous interim fix releases and new fixes for the 6.0.0.1 release.

2.0 Installation information

For information about installing IBM Rational Software Modeler Fix Pack 6.0.0.1, refer to the installation instructions at http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/rsm/60/install_instruction/6.0.0.1/install.html.

2.1 Hardware requirements

There are no additional hardware requirements for installing this fix pack.

2.2 Software requirements

This fix pack can be installed for use with IBM Rational Software Modeler, Version 6.0. Before you can install this fix pack you must install IBM Rational Product Updater 6.0.0.4.

3.0 Fixes in this release

This fix pack contains fixes for problems in the following components:

• Documentation
• General
• Globalization
• Model publishing
• Modeling
• Patterns
• Relational database tools
• Reusable Asset Specifications
• Team programming with Rational ClearCase
• UML diagrams

Documentation

• This release contains the most up-to-date English documentation for Rational Software Modeler.
• The broken links in the modeling cheat sheets have been fixed. All links now reference valid help topics.
• This fix includes updates to the translated versions of the product documentation in French, German, Italian, Brazilian Portuguese, Spanish, Japanese, Korean, Simplified Chinese and Traditional Chinese.
• This fix includes the Auction sample documentation in English and the national languages that were not included in version 6.0.

General

• In the previous release, on non-English system locales, some diagram types in the Properties view are displayed in English when they should be displayed in the appropriate national language. This problem has been fixed.
• In the previous release, on some non-English versions of Windows^®, in the Properties view, text in the General tab is not displayed properly. This problem has been fixed.
• This fix resolves problems with missing or incorrect user interface translations in Korean.

Globalization

Model publishing

• In the previous release, if you click on a state machine from the state chart diagram in the published HTML, the page for the corresponding state machine is not displayed. This problem has been fixed.
• In the previous release, if you click on a call behavior from the activity diagram in the published HTML, the page for the corresponding call behavior is not displayed. This problem has been fixed.
• In the previous release, if you click on a decision from the activity diagram in the published HTML, the page for the selected decision is not displayed. This problem has been fixed.
• In the previous release, if you publish a PDF report with the Automatically display publish output and Always clean destination folder without asking options selected, errors are produced that force you to restart Rational Software Modeler. This problem has been fixed. The published PDF output is now displayed in an external PDF browser.
• The following problem has been fixed: Due to an issue with the default Web browser in Eclipse, when the Automatically display published output check box is selected, the generated HTML or PDF output might not display.

Modeling

• In the previous release, you cannot complete the following operations:
  • Create a port or change type when dragging from the Model Explorer view
  • Change a port type or prompt for a required or provided interface when dragging from the Model Explorer view
  • Create a conjugate port when dragging a connector from a port onto a typed part
  You can now complete these operations.
• In the previous release, the load or import of a UML2 model file might fail. This problem has been fixed.
• In the previous release, model files with cross-model references could not be exported to UML2 or Ecore. Better support for these operations has been included in this release.
• In the previous release, if an attribute is shown as an association and you move that attribute to another class, the attribute connector is not deleted.
• In the previous release, Control Flows on Activity diagrams might be hidden when they should not. This problem has been fixed. The Control Flows are now only hidden for connectors whose ends both exist inside a shape compartment and at least one of the ends is not visible.
• In the previous release, when you set a stereotype attribute type a dialog box might be displayed with the following message: No selection is available. This problem has been fixed.
• In the previous release, if you reconnect an object flow source on an Activity diagram from one output pin to another output pin, the object flow semantic element is deleted. If you then save, close, and re-open the model file, an empty diagram editor opens with Unable to create part. This problem has been fixed.
• In the previous release, if you change the multiplicity from 1 to * in the Properties View for an attribute of a profile stereotype, errors are produced and the operation fails. This problem has been fixed.
• The com.ibm.xtools.modeler.ui.wizards.template extension point allows a plugin to contribute UML template models by referencing a directory within the plugin. However, in the previous release, if the extension references a non-existent plugin directory, then the New Model wizard produces errors. The dialog does not close when you click Finish, nor advance when you click Next. This problem has been fixed.
• The com.ibm.xtools.modeler.ui.wizards.template extension point allows a plugin to contribute UML template models by referencing a directory within the plugin. However, in the previous release, if more than one plugin contributes an extension all template models contributed in this manner appear multiple times in the New Model wizard. The template models appear one time for each plugin declaring the extension. This problem has been fixed.
• The problem has been fixed where full localization was not supported for user-created profiles of a model.
• The problem with the Architectural Discovery rule "Package Local Breakable" where the dependencies between packages are shown in the reverse direction has been fixed.
• The problem where errors are not corrected by the Quick Fix wizard on model validation errors, in the Problems view, has been fixed.
• The following problem has been fixed: When you perform an operation in one model that results in a change to another model, the related cross model reference is not resolved. An unresolved reference appears in a diagram as a circle with a red X through it.
• The following problem has been fixed: If a space or special character is used in the stereotype attribute's name in a profile, a model that has the profile applied might not open.
• The following problem has been fixed: Sharing a project through team support with open UML models is inconsistent with other file location altering actions, such as the Save As functionality. Certain source control settings are ignored.
• The following problem has been fixed: When you compare a model with its local history, and the model contains a pattern with template parameters that point to a deleted model, the comparison fails and an error is logged.
• The problem has been fixed where the export of a model with applied stereotypes, such as a model with documentation, to Ecore would fail and log an error.
• The following problem has been fixed: When you compare or merge versions of a model, certain combinations of deltas and user selections of Accept and Reject can cause data loss. For example, if you accept the move of an element into a new package, but reject the addition of the new package, the moved element is lost.

Patterns

• In the previous release, you could not select 1 or more existing relationships of the types supported by the parameter. This problem has been fixed. An additional tab has been added to the Relationship Parameter dialog that allows you to do so.
• The problem with the pattern parameter HandleRequest from the Chain of Responsibility pattern has been fixed. The pattern parameter now generates the correct Java^™ source code for the operation parameter type after a UML to Java transformation.
• The following problem has been fixed: When a UML model contains a pattern instance with a hard-coded reference to its associated pattern definition, and the model is imported into another instance of Rational Software Modeler, if the hard-coded reference is no longer valid the model does not open.
• The following problem has been fixed: When deployed pattern plug-in projects have missing or re-versioned pattern .rmd files, or missing or deleted parameters from the pattern .rmd file when redeployed to the same location, the project’s .emx file might not open.
• A memory leak in the Pattern Explorer has been fixed.
• The problem has been fixed where, on non-English operating systems, the Model Explorer view displays pattern definitions.

Relational database tools

Reusable Asset Specifications

• In the previous release, no warning message is displayed if a RAS file has a parameter type that does not exist. Instead, a NullPointerException error is produced if you try to expand the pattern node in the Pattern Authoring View. This problem has been fixed.
• In the previous release, when you import a RAS Asset, there is no option for you to display the associated log file. This problem has been fixed. Now, when you import a RAS Asset, you can select a checkbox to indicate whether to display the log file. The log file is displayed in your default web browser.
• In the previous release, if you import a RAS asset that contains multiple plugins, and one of those plugins already exists in your application, errors are produced. This problem has been fixed.
• In the previous release, the RAS import service could not handle certain types of exceptions. To correct the error you had to start the product using the –clean option, which forced you to lose your configuration information. This problem has been fixed.
• In the previous release, the RAS import service produces NullPointerException errors when you attempt to import an asset that contains a related asset with a deployable plugin. This problem has been fixed.
• In the previous release, the dialog that reports errors, warnings, and informational messages when you import or export RAS assets did not support the viewing of details related to the errors, warnings, and informational messages. This problem has been fixed.
• In the previous release, in the RAS Export Wizard, there is no option for you to indicate whether source should be included with the deployable plugins, features, and projects packaged in the RAS asset. This problem has been fixed.
• In the previous release, the RAS export and import functionality does not support the packaging and installing of Eclipse features. This problem has been fixed.
• In the previous release, there is no support for deleting feedback on RAS assets in repositories. This problem has been fixed. This functionality is now included.
• In the previous release, there is no support for click through licensing for assets, artifacts and Eclipse features. This problem has been fixed. This functionality is now included.

Team programming with Rational ClearCase

• The problem where the disablement of the ClearCase^® SCM Adapter capability was not persistent between workbench sessions has been fixed.
• The problem where a dialog prompting for product instance location for the ClearCase Typemanager is presented to the user upon each new workspace creation even if ClearCase is not installed has been fixed.

UML diagrams

• In the previous release, if you attempt to add text to the top of a frame on a State machine or Activity Diagram, or attempt to add a constraint to the top of a fragment on a Sequence Diagram, an error is produced. If, after the error, you save your model file, you cannot open the related diagram and an empty diagram editor opens with Unable to create part. This problem has been fixed.
• In the previous release, if you resize an Alternate Combined Fragment on a Sequence diagram, an error might result forcing you to shut down the application. This problem has been fixed.
• In the previous release, if you delete a stop node that is attached to a destroy message on a Sequence diagram, then delete the remaining message, then attempt to undo the operation, an error is produced and your diagram becomes corrupt. This problem has been fixed.
• In the previous release, you cannot copy and paste information from a Sequence diagram into an external application, such as Microsoft^® Word. This problem has been fixed.
• In the previous release, if a Show Related Elements command encounters an element that has a non-UML relationship, an error is produced. This problem has been fixed.
• In the previous release, operations from implemented interfaces for messages in sequence diagrams could not be selected. This problem has been fixed.
• The problem where the Component shape on a UML diagram did not show a stereotype image has been fixed
• The problem where the top portion of lifeline header names in a UML Sequence Diagram was truncated when using Korean text has been fixed.
• The problem where the top portion of operation names in Compartment shapes of a UML diagram was truncated when using Korean has been fixed.
• The problem that restricted the location of localized UML model profiles to a directory name containing "/profiles". This restriction has been removed.
• The problem where a compare or merge command launched externally by ClearCase on a modeling or visualization artifact failed on Windows Operating Systems set to a language that translates the user's "Application Data" directory has been fixed.
• The problem where changes to the Page Setup dialog for printing UML Diagrams were ignored has been fixed.
• The problem where navigating through a Browse Diagram of Java or UML classes always used the default relationship selections instead of the users last selection has been fixed.
• The default layout preference in the Diagram Navigator of 'Hierarchical' has been changed to 'Flat'.
• The problem where bookmarks on UML Sequence Diagrams would be deleted when geometric shapes were added to the diagram has been fixed.
• The following problem has been fixed: In the Show Related Elements and Topic Diagrams features, the user might click a stopping condition in the stopping list for the purposes of traceability. When either the Implementation or Specifications item in the list is clicked, the correct result is not obtained.
• The problem has been fixed where a connector would disappear or not be shown on an Activity diagram if it crossed a partition.

4.0 Known limitations, problems, and workarounds

This readme includes release-specific information, such as problems and limitations that were not available until after the product documentation was finalized.

4.1 Limitations

4.2 Problems and workarounds

5.0 Contacting customer support

The product home page for Rational Software Modeler is www.ibm.com/software/awdtools/modeler/swmodeler/. For FAQs, lists of known problems and fixes, and other support information, visit the Support page on the product home page.

6.0 Notices and trademarks

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Intellectual Property Dept. for Rational Software
IBM Corporation
20 Maguire Road
Lexington, MA
02421-3112
USA

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 2000, 2005. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Programming interface information

Programming interface information is intended to help you create application software using this program.

General-use programming interfaces allow you to write application software that obtain the services of this program's tools.

However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software.

Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.

Trademarks and service marks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:

• ClearCase
• developerWorks
• IBM
• Rational
• Rational Rose
• RequisitePro
• SoDA
• WebSphere
• XDE

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel is a trademark of Intel Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.