Follow these guidelines before installing Rational Rose on your system:

• Ensure that other windows programs are not running.

• Back up your Registry and system directories prior to running the installation program. In addition, make system back ups of any machines on which you plan to install this software. Specifically, we recommend you make back ups of the following files:

• Model files
  You should always have a back up of all your model files. These can include files that end with .mdl,.cat,.ptl, .red, and .sub files.

• Custom property files
  These can include files that end with .pty .prp

Note: There is no need to save .pty files that ship with Rose, since these will be reinstalled.

• Custom script files
  Files that end with .ebs .ebx

Note: There is no need to save .ebs or .ebx files that ship with Rose, since these will be reinstalled.

• Path Maps
  Rose 98,98i,2000 path map variables are saved in the registry.
  To backup path map variables:

1. Run regedit and navigate to HKEY_CURRENT_USER\Software\Rational Software\Rose\Virtual Path Map
2. Click Registry > Export Registry File...

To restore path map variables:

1. Run regedit and navigate to HKEY_CURRENT_USER\Software\Rational Software\Rose\Virtual Path Map
2. Click Registry > Import Registry File... and import the file you exported.

• You may install Rose 2000e over a previous version of Rose and the installation process will install the Rose files in the Rose directory. The install of Rose 2000e will remove the old subdirectory (e.g., \98i) before copying in the new files and the install will update the Start > Programs menu. However, the install will retain all user created files in the old Rose directory (e.g., \Rational\98i for Rose 98i). You will not be able to run two different versions of Rose on the same machine.
• You must have local administrator privileges to install this software (both Rose and the License Server) on an NT machine.

Before you install Rational Rose, please verify that your system meets the minimum system requirements listed below. If you do not have the correct operating system level, the product may not install correctly.

The hardware requirements for Rose 2000e are:

Processor A Pentium-based 150 Mhz, PC-compatible computer system

Memory 128MB recommended, 64 MB minimum (Memory requirements increase with the size of the model)

Disk space 200MB (100 Rose, 100 download/install)

Other An SVGA-compatible display (256 or more colors recommended) with the resolution set at 800 X 600 pixels.

Any pointing device with at least two buttons

Rose 2000e will run on the following operating system platforms:

• Windows 95 Retail Version - Service Pack 1
• Windows 95 OEM Version - OSR 2.1
• Windows 98
• Windows NT 4.0 - Service Pack 3
• Windows NT 4.0 - Service Pack 4
• Windows NT 4.0 – Service Pack 5
• Windows 2000 RC1

Rose 2000e requires DCOM under Windows 95. If you do not have DCOM on your Windows 95 system, the install will point you to the Microsoft web site to obtain the software.

The VC++ Add-In requires Visual Studio 6.0.

The Rose J add-in requires JDK 1.1.6 or any of the major Java IDEs.

The Globetrotter FLEXlm license server component, which is required for floating licenses, will run on Windows NT 4.0 (with Service Pack 3 or greater) only. It is not designed to run on Windows 9X; however the installation will not prevent you from installing it under Windows 9X. Client licensing will run on both Windows 9X and Windows NT.

Please refer to the Rose 2000e Installation Guide , as well as Administering Licenses for Rational Software, which are provided as your primary guides for installing and setting up licensing for Rational Rose.

If you encounter a problem while installing or licensing the Rose product, please check the Known Install / Uninstall Issues in this Release Note for information. If the problem is not yet documented, please contact Rational Technical Support so that we can investigate the problem, provide you with a workaround, and track the problem for future action.

For information on installation defects that have been fixed, see Install Defects Fixed Since the Last Release

The documentation CD contains supplemental product material such as tutorials, models, and user manuals. All the supplemental material for Rational Rose is located under the Rational Rose directory on the CD.

Additional Licensing Issues

• Installing the FlexLM License Server on a machine that already has FlexLM
• Distributing floating licenses to more than one server

• We do not support moving node-locked licenses from one machine to another in this release.

The word "Rational" and Rational's products are trademarks of Rational Software Corporation. References to other companies and their products use trademarks owned by the respective companies and are for reference purposes only.

© Copyright 2000 Rational Software Corporation.

Thank you for choosing Rational Rose 2000e. The Rational Rose 2000e release notes contain information about last-minute changes to Rational Rose and the Rational Rose Add-Ins. Refer to the readme.txt file, located on the start menu, for last-second changes not available when the hardcopy and online versions of the release notes were published.

To view the release notes for Rational Rose 2000e, select one of the following links:

• Rational Rose
• Rose Extensibilitiy Interface

To view the release notes on any of the Rational Rose Add-Ins, select the appropriate links:

• C++ Add-In
• ClearCase Add-In
• Corba Add-In
• Data Modeler Add-In
• Framework Wizard Add-In
• Oracle8 Add-In
• Rose J Add-In
• Model Integrator Add-In
• Type Library Importer Add-In
• Version Control Add-In
• Visual Basic Add-In
• Visual C++ Add-In
• Web Modeler Overview
• Web Publisher Add-In
• XML Overview

Rational Rose, the world's leading visual modeling tool, allows you to define and communicate a software architecture, resulting in accelerated development, improved quality, and increased visibility and predictability.

The Rational Rose release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Rational Rose 2000e release note information at the following locations:

New Rational Rose Features and Enhancements

Rational Rose Tutorial

Known Rational Rose Problems and Limitations

Rational Rose Defects Fixed since the Previous Release

Technical Support

Trademark Information

The following list describes the new features added for the Rose 2000e release:

• Subsystem Stereotype Package

Subsystem is now a predefined stereotype that is available for packages.

The following features and enhancements are new for the Rose 2000e release of the Rose Extensibility Interface (REI).

New Object and Object Flow Capabilities of Activity Diagrams

• Add, delete, retrieve object flows between activities and objects using:

• Activity.AddObjectFlow
• Activity.DeleteObjectFlow
• Activity.GetObjectFlows
• ObjectInstance.AddObjectFlow
• ObjectInstance.DeleteObjectFlow
• ObjectInstance.GetObjectFlows

• Retrieve and set an object flow’s state

• ObjectFlow.GetState
• ObjectFlow.SetState

• Add, retrieve, and remove views of objects using:

• StateDiagram.AddObjectInstanceView
• StateDiagram.GetDiagramObjectInstanceViews
• StateDiagram.GetObjectInstanceViews
• StateDiagram.RemoveObjectInstanceView

• Add, delete, and retrieve objects using:

• StateMachine.ObjectInstances
• StateMachine.AddObjectInstance
• StateMachine.DeleteObjectInstance
• StateMachine.GetAllObjectInstances

New Data Modeling Capabilities

• Add data modeling diagrams using Category.AddDataModelDiagram
• Determine if a diagram is a data modeling diagram using ClassDiagram.IsDataModelingDiagram

New Dependency Relationship Capabilities

• Add, delete, retrieve dependency relationships using the DependencyRelation class with existing Relationship properties and methods

New Capabilities for Working with Models and Controlled Units

• Determine whether a save was successful using Application.SaveModel
• Import packages and subsystems into the current model using Model.Import
• Load specified unloaded controlled units into a model using Model.LoadControlledUnits

• For a class view object on a diagram, toggle the display of access adornments on attributes and operations using ClassView.Visibility
• For a class view on a diagram, determine whether the access adornments of the attributes and operations are visible using ClassView.Visibility

• Specify stereotype display using RoseItemView.StereotypeDisplay and RoseItemView.StereotypeDisplay
• Remove item views from diagrams using Diagram.RemoveItemView
• Retrieve selected diagrams using Model.GetSelectedDiagrams
• Link diagrams to a note view using NoteView.LinkDiagram
• Retrieve attached notes using RoseItemView.GetAttachedNotes

Other New Capabilities

• Retrieve the parent (context) item of a state machine owner using StateMachineOwner.GetParentItem
• Retrieve the fully qualified names of the unloaded components to which a class is assigned using Class.GetAssignedUnloadedComponents

New and Updated COM Event Information

• Using OnModifiedModelElement to be notified that a model element has changed now returns more modification reasons
• Using OnModifiedModelElementEx to be notified that a model element has changed now returns a new event, which returns additional information such as the old stereotype or the former context (parent) of the modified element.
• Using OnDeletedModelElementEx to be notified that a model element has been deleted now returns a new event, which returns the parent or context of the deleted model element.

The Rose 2000e release continues to include the Rose tutorial. The tutorial is distributed as a self-extracting archive file that is meant to be placed on the hard drive of the machine where Rose 2000e is installed.

The filename is RoseTutorialFiles.exe and is located on the Rational Solutions for Windows Online Documentation CD in the \RationalRose\Tutorials\Rose 2000 directory.

This file is approximately 4MB in size. When extracted, it requires approximately 28MB of free disk space. Refer to the Tutorial Read Me file located on the Start menu for more tutorial information.

The Rose 2000 tutorial:

• Teaches you how to use Rational Rose to model a robust, easily understandable n-tier, multi-language application
• Introduces you to the main Rose features
• Exposes you to Visual Modeling concepts using the UML in the context of Rational Rose
• Maintains a common terminology with the Rational Unified Process (RUP)

Please keep in mind that the self-extracting file that contains the tutorial does not uninstall when you uninstall rose from your system. You must uninstall the tutorial files when you uninstall Rose.

For best viewing of the tutorial, set your display's Color Palette to True Color or the highest number of colors possible (click Start > Settings > Control Panel > Display > Settings).

The Repository Add-In is no longer a supported feature of Rational Rose; however, the add-in is included with the release to support customers’ legacy requirements.

To obtain source code for the Repository Add-In, go to the Download Center on Rational Rose’s Product Support page and follow the links to the Repository code.

The following list describes the known problems and limitations of Rational Rose 2000e or its extensibility interface (REI):

The following defects have been fixed since the previous release of Rational Rose.

Rose Ada Add-In (Overview)

The Rose Ada add-in allows you to produce Ada source code from the information contained in a Rose model.

The code generated for each selected model component is a function of that component's specification and code-generation properties, and the model's properties. These properties provide the language-specific information required to map your model onto Ada.

Rose/Ada preserves user-supplied declarations and statements from one iteration to the next. You place such user-supplied code in protected code regions which are preserved whenever code is re-generated.

The Rose/Ada Code Generator

New Rose Ada Features and Enhancements

The following list describes the new features and enhancements for the Rose 2000e release:

• With one or more model units which have been assigned to the Ada 83 or Ada 95 languages selected, a right click will display a context menu with a new language specific popup menu containing code generation and browse header/body menu items.

• A new code generation dialog has been added to control whether Subsystems and Views should be generated and whether code should be generated. This allows Subsystems and Views to be generated first and then subsequently only do generation of Ada units. Note that Subsystems and View must be generated before any Ada unit, otherwise the directory structure is not set up to support Apex commands.

Known Rose Ada Problems and Limitations

The following list describes the known problems and limitations for the Rose 2000e release:

• During installation of Apex NT 2.0.2, the Update Environment option must be set.
• The Apex command accept_import_changes is not yet supported in version 2.0.2 of Apex NT. This affects the Subsystems and Views generation of the Ada add-in that imports are not setup in the created views.

Rose Ada Defects Fixed Since the Previous Release

The following defects have been fixed since the previous Rose Ada release.

Corba Add-In (Overview)

Rational Rose Corba Add-In allows you to forward engineer Rose model elements into Corba-compliant IDL code and it allows you to reverse engineer CORBA IDL code into appropriate Rose model elements.

The Corba Add-In release notes describe new features and enhancements, upgrade information, known problems and limitations, and fixed defects since the last release.

You can find Corba Add-In release note information at the following locations:

• New Corba Add-In Features and Enhancements
• Known Corba Add-In Problems and Limitations
• Corba Add-In Defects Fixed since the Previous Release

Technical Support

Trademark Information

New Corba Add-In Features and Enhancements

There are no new features in the Rose 2000e version of the CORBA Add-In.

Known Corba Add-In Problems and Limitations

Corba Add-In Defects Fixed since the Previous Release

There are no known defects fixed since the previous release.

C++ Add-In (Overview)

Using the Rational Rose C++ Add-In, you can produce C++ source code from the information contained in a Rational Rose model. The code generated for each selected model component is a function of that component’s specification and code generation properties, and the project’s properties. These properties provide the language-specific information required mapping your model onto C++, and allow you to control the code generated for each component.

You can find C++ Add-In release note information in the following locations:

The following additional feature information, although not new, is provided in the release note because it is not yet incorporated into the regular Rose C++ documentation:

Trademark Information

Upgrading from a Previous C++ Add-In Release

There is one aspect of the Rose 2000e C++ Add-In Code Generator that you should understand when upgrading. A version stamp in the generated code allows you to stay in control when regenerating code of a different version. Refer to the C++ Code Generator Versioning topic to learn more about this feature.

C++ Version Comment Orphaned

If you are using an older, version stamp unaware code generator to update version stamped code (C++ code generator versioning) the version stamp comment will end up in the orphaned section at the end of the module. This raises the same issues as described in the C++ annotation downgrade topic. The recommended action is to use the newer code generator.

It is likely that other preserved regions will also end up in the orphaned section. If you decide to undo this operation, you will have to manually revive the written backup files.

C++ Minor Version Downgrade

A minor version downgrade occurs when you update code that had been written with a newer code generator, which supports the same annotation format.

Minor downgrades may introduce problem if your current model/code depends on capabilities that have been introduced in the newer code generator. Note that minor upgrading will remedy those problems. Therefore minor downgrades will not raise problems which may require manual work. However, you should allow the downgrade only if you are sufficiently certain that you are not causing problems.

The capability to honor a minor version attempt can be controlled in the same way as the annotation version downgrade. So even though minor downgrading is far more reasonable, the behavior regarding error/warning messages and default setting is the same. Setting the Boolean project property AllowGenerateOverNewerVersion to True will allow you to perform the downgrade. The code generator will still issue a warning in order to make you aware of the potentially unintended downgrade.

C++ Code Generator Versioning

C++ Code Generator Versioning

The C++ code generator uses annotations (protected regions) in the code in order to support non-destructive code regeneration (code updating). The C++ Analyzer takes advantage of the annotations as well.

As the code generator advances using code generators of different versions, the same code base becomes problematic. This is the case when the annotations format changes. A code generator versioning stamp and a surrounding mechanism has been introduced to address this problem.

A particular code generator version will only write the newest version of annotations. However, it can read and interpret older versions of the prior annotation version. How far the backward compatibility goes depends on the kind of change introduced. The code generator will issue a warning message when an annotation upgrade occurs. Refer to the C++ Annotation Upgrade topic to read more about the implications of upgrading the annotation format. Upgrading to a higher minor version is the recommended path and does not cause any problem because it does not require any transformations. The annotation format has not changed.

There are some additional considerations when using an older code generator that is not aware of version stamps. The first version of the version stamp aware code generator is version 1.1. If it does not find a version stamp, it will assume that the file had been written by an older code generator. The behavior is as if found a stamp denoting version 0.0. The C++ version comment orphaned topic contains more information about the effects when using a version 0.0 code generator on newer version stamped code.

• C++ Version Comment Orphaned
• C++ Annotation Upgrade
• C++ Annotation Downgrade
• C++ Minor Version Downgrade

C++ Annotation Upgrade

A major annotation upgrade happens when code is updated that had been written with an older code generator that supports an older annotations format.

An annotation upgrade is introduced to put more information in the code in order to find preserved regions properly in complex situations. For example, support for recognizing the preserved regions for property generated operations (such as assignment operators) copy constructor when the class name changes.

Changing the annotation format has disadvantages, which is the reason why they occur only after careful consideration of alternatives. One disadvantage is that upgrading to a new format can create problems if the upgrade occurs at the wrong time. Whether this is true or not depends on the particular format change introduced. In addition, upgrading is in general restricted to a particular number of versions.

A particular code generator will support upgrading from the next lower annotation version under stable conditions. Stable conditions means that the upgrade should occur on code that has been successfully updated using the code generator from which to upgrade. If the current code does not fit the model, upgrading and synchronizing at the same time may fail. The steps to assure stable conditions are:

1. Update the code with the code generator version you want to update from.
2. Do not change the code and the model.
3. Update the code with the target code generator version.

C++ Annotation Downgrade

A major annotation downgrade occurs when you update code that had been written with a newer code generator supporting a newer annotation format.

Refer to the C++ annotation upgrade topic for reasons why the annotations format may change. It must be expected that the older code generator may not be able to recognize the code regions with the newer annotation. It is particularly problematic to share code using code generators, which support different annotation versions. The exact risk depends on the usage of newer code generator features and how models and especially the produced code are going to be shared.

Downgrading annotations is neither recommended nor automatically supported. You may have to do manual work.

C++ Code Generator Versioning

Known C++ Add-In Problems and Limitations

C++ Add-In Defects Fixed since the Previous Release

The following defects have been fixed since the previous release:

ClearCase Add-In (Overview)

The ClearCase Add-In provides a tight integration between Rational Rose and the Rational ClearCase version control system. This add-in is intended as a replacement for the ClearCase capabilities provided through the generic Version Control Add-In. Unlike the Version Control Add-In, the ClearCase Add-In does not use the Microsoft SCC API to communicate with ClearCase. This allows for more ClearCase-specific customization to this add-in.

If you are already familiar with the Version Control Add-In, you should find the transition to the ClearCase Add-In simple because the majority of the dialogs and menu items are identical.

The ClearCase Add-In release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release:

Trademark Information

New Clear Case Add-In Features and Enhancements

The new features and enhancements of the Rose 2000e version of the ClearCase add-in are:

Known Clear Case Add-In Problems and Limitations

Clear Case Add-In Defects Fixed since the Previous Release

The following Clear Case Add-In defects have been fixed since last release:

Data Modeler Add-In (Overview)

Data Modeler supports round-trip engineering. From the data model, it can forward-engineer SQL DDL to a DDL file or a database. It can also reverse-engineer data models directly from an existing database or DDL file. In addition, it can transform a data model into an object model to build an application or transform an object model into a data model to connect to a database.

Data Modeler release note information is available in the following locations:

• Data Modeler Features
• Known Data Modeler Defects and Limitations

Technical Support

Trademark Information

Data Modeler Add-In Features

The following describes the Data Modeler Add-In features that are available for the Rose 2000e release.

Databases

Data Modeler supports the following DBMSs and SQL standard:

• DB2 MVS and UDB 5.x, 6.x
• Oracle 7.x and 8.x
• Microsoft SQL Server 6.5 and 7.0
• ANSI SQL 92

Rose Data Modeler requires access to the DBMS tool set for the database(s) you are modeling.

Data Model Elements

Data Modeler allows you to create, edit, and delete the following elements:

• Database
• Schema
• Table
• Trigger
• Column
• Constraint (primary, foreign, unique, check)
• Index

Data Modeler can reverse-engineer a DDL script or database directly into a data model. You can also forward-engineer a DDL script or database from an existing data model.

System-generated triggers as RI constraints (DB2, Oracle, SQL)

Database Compare (with a DDL script file or a database)

Data Modeler can compare a schema in a data model with an external database or DDL script. This feature provides a detailed report on the differences between the data model and database or script file, so that you can begin to implement changes.

Customized Specification Dialogs

The Specification dialog boxes allow you to set some model properties, edit existing specifications, and in some cases create certain elements. Data Modeler uses the following Specification dialog boxes:

• Table Specification
• Column Specification
• Database Specification
• Schema Specification
• Relationship Specification

Data Model to Object Model Transformation

This feature allows you to use an existing data model and transform it into an object model that uses Analysis language.

Object Model to Data Model Transformation

This feature allows you to use an existing object model and transform it into a data model.

Toolbox and Diagram Integration

Data Modeler uses its own customized toolbox that allows you to:

• Add a table
• Add an identifying relationship
• Add a non-identifying relationship

Automatic Key Migration

With the exception of deleting or renaming a model element, Data Modeler provides automatic key migration for the following actions:

• Add a relationship
• Change a relationship’s type (identifying to non-identifying)
• Change primary key column’s data type
• Add or remove a column from a key constraint
• Reorder the composite key’s order
• Delete a column that is part of key constraint
• Delete a key constraint
• Delete a relationship

Browser Customization

The Data Modeler browser is customized from the original Rational Rose browser.

• Data Modeler uses Schema, the Logical View’s root package, as a primary container.
• Data Modeler replaces irrelevant object modeling context menus and specification dialogs with customized data modeling menus and specifications.
• Overload visibility icons for column types (PK, FK, PK/FK, None).
• Customized stereotype icons for database, schema, and table.

Known Data Modeler Defects and Limitations

Framework Wizard Add-In (Overview)

The Framework Add-In provides a library of frameworks that can be used as templates when creating new models. The Framework Add-In also provides a wizard that helps you add additional frameworks.

The Framework Wizard Add-In release note describes new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Framework Wizard Add-In release note information in the following locations:

• New Framework Wizard Features and Enhancements
• Known Framework Wizard Problems and Limitations
• Defects Fixed since the Last Release

Technical Support

Trademark Information

New Framework Wizard Add-In Features and Enhancements

The Framework Wizard Add-In functionality has not been enhanced in Rational Rose 2000e.

Known Framework Wizard Add-In Problems and Limitations

Framework Wizard Add-In Defects Fixed since the Previous Release

No known defects have been fixed since the previous release.

Oracle8 Add-In (Overview)

Rational Rose Oracle8 enables you to create object models from Oracle8 relational schemas and extend them to exploit Oracle8’s object capabilities.

Rational Rose Oracle8 visualizes existing relational databases and facilitates the discovery and composition of existing business objects. This enables you to preserve your investment in existing relational databases while taking advantage of all the benefits that object modeling and development bring to desktop and server applications.

The Oracle8 Add-In release note describes known problems and limitations and fixed defects since the last release. The Rational Rose 2000e Oracle8 Add-In only includes defect fixes. It does not include any new features.

You can find Rational Rose Oracle8 release note information at the following locations:

Technical Support

Trademark Information

Known Oracle8 Add-In Problems and Limitations

Oracle8 Add-In Defects Fixed since the Previous Release

There are no known defects fixed since the previous release.

Version Control Add-In (Overview)

The Version Control Add-In, formerly known as the Source Code Control Add-In, provides integration between Rational Rose and any SCC-compliant version control system. It makes the most frequently used version control commands accessible directly from the Tools menu and from shortcut menus in Rose.

The Version Control Add-In release notes describe new features and enhancements, upgrading information, known problems and limitations, and fixed defects since the last release.

Trademark Information

New Version Control Add-In Features and Enhancements

There are no new features in the Rose 2000e release of the Version Control Add-In. However, the ClearCase Add-In has several new features.

Upgrading from the Visual SourceSafe Add-In

The specific Visual SourceSafe (VSS) integration available in Rose 98i was incorporated into the Version Control Add-In in the Rose 2000 release. This Add-In now handles a super set of the VSS specific features. To upgrade a model that has been put under version control through the VSS Add-In, use the following steps:

As the model is already under version control, the Version Control Add-In only updates the controlled units with additional version control information. From now on you can use the Version Control commands to check out and check in the units.

Known Version Control Add-In Problems and Limitations

Version Control Add-In Defects Fixed since the Previous Release

No known defects have been fixed since the previous release.

Type Library Importer Add-In (Overview)

The Type Library Importer Add-In allows you to import a type library of a COM component into the model by dragging the COM component from Windows Explorer and dropping it in Rational Rose.

You can control several aspects of how type libraries are imported into the model. For example, you can control:

• What should happen with existing type libraries when importing new versions
• The name and location of new type libraries in the model
• The name and contents of the overview diagrams that are created when importing type libraries.

The Type Library Importer Add-In release note describes new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Type Library Importer release note information in the following locations:

• New Type Library Importer Features and Enhancements
• Known Type Library Importer Problems and Limitations
• Type Library Importer Add-In Defects Fixed

Technical Support

Trademark Information

New Type Library Importer Features and Enhancements

Composition hierarchies may optionally be constructed in the model when importing Type Library information

A composition hierarchy is built by defining associations between interfaces and coclasses. The associations are derived from the types of the properties exposed from the interfaces.

To get the information constructed in the model, select the Construct Composition Hierarchy in the COM properties dialog box.

Known Type Library Importer Problems and Limitations

There are no known Type Library Importer problems for the Rose 2000e release.

Type Library Importer Add-In Defects Fixed

Model Integrator Add-in (Overview)

The Rose Model Integrator Add-In lets you compare model elements from up to seven contributor files, discover their differences, and merge them into the base model.

The Model Integrator Add-In release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Model Integrator Add-In release note information at the following locations:

• Model Integrator Add-In Features and Enhancements
• Known Model Integrator Add-In Problems and Limitations
• Model Integrator Add-In Defects Fixed since the Previous Release

Technical Support

Trademark Information

New Model Integrator Add-In Features and Enhancements

Enhanced Merge Mode User Interface

In Merge mode, several enhancements to the user interface make Model Integrator much easier to use:

• The Compare mode icon column (C column) is newly added to the Merge mode browser window. This makes it possible to see both changes and conflicts in the merged model without switching modes.
• The Edit > Undo and Redo capability is enhanced to allow infinite undo and redo (up to the limits of available memory).
• An Edit > Search function allows you to search for any model element displayed in the model browser window.
• View > Expand and View > Elide commands allow you to select a set of model elements in the browser or property windows and expand or elide their subordinate nodes in the tree without having to click on each one individually.
• The Options > Auto Advance function is enhanced to allow Auto Advance to operate over either conflicts or differences, or to be disabled. The toolbar button for Auto Advance has been replaced with a button that activates Subtree mode (see below for a description).
• The View menu commands (and corresponding toolbar buttons) for navigating conflicts and are enhanced to offer different options depending on the current Options > Auto Advance mode. When Auto Advance mode is set to Conflicts, the View > First Conflict and View > Last Conflict commands will take you to the first and last conflicts in the model. When the mode is set to Differences, these same commands take you to the first and last differences in the model. When the mode is set to None, these commands take you to the first and last nodes of the model, and the View > Next and View > Previous commands take you to the next and previous nodes of the model.
• The View > Referenced Node command allows you to follow references from the current node of the model to other parts of the model. This eliminates guess work when tracking down problems with interrelated model elements.
• Options > Hide Deleted Nodes will hide deleted nodes from the browser window, making it easier to see exactly what the merged model will look like when saved.

New Merge Capabilities

Merge commands are enhanced to allow new merging capabilities. Model Integrator now allows you to accept changes from any contributor wherever a difference is detected. Previous versions only permitted changes where a conflict between the merging files was detected.

• Merge > Resolve All Conflicts Using… is modified to operate only on unresolved conflicts. This makes it possible to make some changes by hand, and then resolve the remaining conflicts to a particular contributor without overwriting your previous choices. This command does not operate over differences.
• Merge > Resolve Selected Nodes Using… is modified to operate on any node of the model which has changed (these nodes display a difference icon in the C column of the browser window; they may or may not also display a conflict icon in the M column). Applying this command causes Model Integrator to copy the model element and all of its properties from the selected contributor to the merged output. A number icon signifying the contributor number selected is displayed in the M column for this node. This command can also operate in Subtree mode, described below.
• Merge > Revert Selection takes the selected nodes back to the unmerged state they were in when first loaded by Model Integrator. This command is most useful in a long merge session, when you want to override your previous merge selections and return to Model Integrator’s default behavior. This command works with Merge > AutoMerge. It also works with Subtree mode, described below.
• Merge > AutoMerge applies the standard Model Integrator AutoMerge procedure to the selected nodes. This same command is applied to the whole model when merge mode is first entered. It will have no effect on any model elements unless the Merge > Revert Selection command has already been applied to them.
• Subtree mode is an operating mode for merge mode commands that applies the current command to both the currently selected nodes and all of their subordinate (or child) nodes. For example, if you enable Subtree mode and then use the Resolve Selected Nodes command to select contributor 2 for a diagram, contributor 2 will be selected for all the component elements of the diagram as well. This can save you a lot of work when there are a lot of related changes and you want to select them all from the same contributor. Subtree mode has a new evergreen tree icon on the toolbar which shows when it is active.

Enhanced Semantic Checking

Model Integrator preserves consistency in your merged models by performing semantic checks to find nodes of the model that have dangling references to other nodes that have been moved or deleted. This function is performed automatically before the model is saved, and you can also perform this check yourself anytime during a merge session by using the Merge > Check Merge command. This feature was present in the last release but it has been enhanced to provide a more thorough check.

A new capability in this release is the Merge > Semantic Checking menu selection. This selection toggles the on-the-fly semantic checking function on and off. On-the-fly semantic checking helps you to make valid merge choices when merging models by checking each of the contributors for the current node and disabling those contributors which could result in a dangling reference. Using this function is optional, and it does not eliminate the need for checking the merged file or the possibility of introducing errors that must be repaired, but it can help you to reduce time spent chasing down merge errors.

Merging Without a Base Model

Model Integrator is typically used in an environment where two or more branches of a model under version control are being merged to produce a new integrated version for the main branch of the model. Model Integrator optimizes the merge for this situation by requiring a base model which is the ancestor of the models being merged. However, when merging unrelated model files, no ancestor model exists to provide the base model. Now Model Integrator provides a check box in the Contributors dialog that, when checked, enables the standard behavior. When unchecked, Model Integrator creates an empty base model for you. This results in the correct behavior when merging unrelated models. Previous versions of Model Integrator required you to create an empty base model in Rose and then use it in the merge.

Streamlined Subunit Save Handling

Model Integrator streamlines the typical case of saving models with subunits by saving your current subunit configuration "as is" when using the File > Save command or toolbar button. You can still alter your subunit configuration using the Subunits dialog when saving models by using the File > Save As command. Previous versions of Model Integrator always brought up the Subunits dialog when saving a model, whether it had subunits or not.

Revised Help

The help documentation for Model Integrator has been completely revised and greatly expanded for this release.

Known Model Integrator Add-In Problems and Limitations

Model Integrator Add-In Defects Fixed since the Previous Release

Rose J Add-In (Overview)

The Rose J Add-In supports true round-trip engineering and has support for large frameworks. The Rose J release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Rose J release note information at the following locations:

• New Rose J Add-In Features and Enhancements
• Known Rose J Add-In Problems and Limitations
• Rose J Add-In Defects Fixed since the Previous Release

Technical Support

Trademark Information

New Rose J Add-In Features and Enhancements

The Rational Rose 2000e version of Rose J provides a link to IBM VisualAge for Java™. Refer to the Rose J online help for detailed information.

It also provides an integration with Enterprise Java Beans. This integration provides a UML Bridge tool, which allows forward and reverse engineering between Rose models and Enterprise Java Beans.

Known Rose J Add-In Problems and Limitations

There are no known Rose J defects for this release.

Rose J Add-In Defects Fixed Snce the Previous Release

The following list describes the defects fixed since the previous release.

Visual Basic Add-In (Overview)

The Visual Basic Language Support Add-In enables Rational Rose to model, generate, and reverse engineer code for applications written in Microsoft Visual Basic. The Visual Basic Language Support Add-In tools in Rose are tightly integrated with the Microsoft Visual Basic environment, allowing you to seamlessly progress through the round-trip engineering process.

The Visual Basic Add-In release note describes new features and enhancements, known problems and limitations, and fixed defects since the last release.

The Visual Basic Add-In tools are:

• Class Wizard
• Model Assistant
• Component Assignment Tool
• Code Update Tool
• Model Update Tool

You can find Visual Basic Add-In release note information in the following locations:

• New Visual Basic Add-In Features and Enhancements
• Upgrading from a Previous Visual Basic Add-In Release
• Known Visual Basic Problems and Limitations
• Visual Basic Add-In Defects Fixed

Technical Support

Trademark Information

New Visual Basic Add-In Features and Enhancements

VB project and the compiled COM component in the same model

In Rose 2000e you can have both a VB project component and its compiled COM component in the same model. You can import the type library of the compiled COM component either manually, for example by drag and drop, or automatically, by selecting the new option "Import the compiled VB binary" in the Visual Basic Component Properties dialog box before updating the model from the project.

The VB project is represented as a component with the language Visual Basic and a stereotype that corresponds to the project type, just as before. The type library of its imported COM component is represented as a component with the language and stereotype COM.

Enhanced web class support

The Visual Basic add-in in Rose 2000e supports round-trip engineering of web classes. Web classes, web items, and web item events can be both generated and reverse engineered. The web items on a web class are represented as nested classes in the web class, with the stereotype Custom WebItem or Template WebItem. A web class’s web items can be viewed and created in a new folder called Web Items, in the Model Assistant, as well as on the Nested tab of the web class.

Enhanced template mechanism

The Visual Basic class template mechanism has been enhanced and is now used also for Visual C++ classes. The enhancement means, for example, that:

• Script code is used in the template member files, which makes the templates even more flexible.
• Template member file can include the contents of another file.
• When applying a template to a class in the model, dependencies to other classes can be established automatically. For example, a template can use a COM type library, realize an interface class, or use another class.

Information on how to create and modify templates is available in the Rose Visual Studio RTE Extensibility online help book, under the Rational Rose Extensibility Interface book on the Contents tab of the Rose online help.

Rose Visual Studio RTE Extensibility interface

The Visual Studio round-trip engineering tools—Code Update Tool, Model Update Tool, Model Assistant, and the template mechanism—can be extended in Rose 2000e by using their exposed and documented API. For example, you can run the Code and Model Update tools in hidden mode from a script or program.

The Visual Studio RTE API is documented in the Rose Visual Studio RTE Extensibility online help book, which is found under the Rational Rose Extensibility Interface book on the Contents tab of the Rose online help. The online help provides samples on how to extend the Visual Studio round-trip engineering tools.

Model Assistant performance improved

The performance of the Model Assistant has been improved. The improvement means that the changes you make in the Model Assistant directly affect the model. Thus, the Cancel and Apply buttons have been removed.

No VB5 support

The Rational Rose 2000e version of the Visual Basic add-in supports VB6. Thus, VB5 is no longer supported.

EntryCode and ExitCode model properties not supported

The EntryCode and ExitCode model properties on methods (operations) are not provided in Rose 2000e. These model properties are no longer inserted into the default body of methods. To add standard entry and exit code to methods, enter the required piece of code into the method templates (.rvb files).

Composition hierarchies may optionally be constructed in the model when importing Type Library information

A composition hierarchy is built by creating associations between interfaces and coclasses. The associations are derived from the types of the properties exposed from the interfaces. Make sure that the Construct Composition Hierarchy in the COM properties dialog box is selected to get the information constructed in the mode.

Default Instancing property value for new classes

New classes created in the model will now get the Instancing property set to MultiUse. In previous Rose releases the default value was Private.

Default stereotype on new components

New components created in the model will have the stereotype set by default to ActiveX DLL. When created in code, the startup object in the project will be set to "(none)".

Debug and Error Handling options are turned off by default

The option to get Debug code and Error Handling code generated into new Visual Basic project has been turned off by default.

Upgrading from a Previous Visual Basic Add-In Release

Models and Visual Basic code created and generated in Rose98i, Rose 98i Service Pack 1, and Rose 2000 are compatible with Rose 2000e; that is, the Visual Basic classes in old models and the corresponding Visual Basic projects do not need to be upgraded for Rose 2000e.

However, Rose 2000 template files that were created by the user need to be upgraded manually.

Known Visual Basic Add-In Problems and Limitations

Visual Basic Add-In Defects Fixed since the Previous Release

The following defects have been fixed for Rational Rose 2000e:

Visual C++ Add-In (Overview)

The Rational Rose Visual C++ Add-In provides the interface between the Rational Rose modeling environment and Microsoft Visual C++. The main features of Rational Rose Visual C++ include:

You can find Rational Rose 2000e Visual C++ Add-In release note information at the following locations:

Trademark Information

New Visual C++ Add-In Features and Enhancements

New Features and Enhancements

You can quickly import the classes from the ATL 3.0 library into your model. Use Tools > Visual C++ > Quick Import ATL 3.0.

This release adds significant enhancement to the support for modeling MIDL coclasses and interfaces.

You can now round-trip engineer coclasses and interfaces independent of the C++ classes in a project. Each .idl file in a project will be modeled by a separate component in the Rose model. This makes Rose MIDL support more appealing to the Visual Basic developers who want to use MIDL to define their COM interfaces but do not want to program in Visual C++.

The Rose Model Assistant now supports coclasses, interfaces, and dispinterfaces. The Model Assistant lets you navigate from an ATL class in your model directly to the coclass and interfaces it implements. You can add new methods and properties to your interfaces with the Model Assistant.

Rose now supports MIDL round-trip engineering at the .idl source file level. Previously, the Rose Model Update tool would compile a project’s .idl file and use the Typelib Importer to bring the resulting .tlb file into the model. In this release both Model Update and Code Update use the .idl file directly. This results in improved model-to-code consistency.

A code template lets you predefine a "pattern" for a class. This pattern can contain both the UML structural description of a class (for example, operations and attributes) and the actual code you want generated for the class and its members.

There are times in the software development process when you want to reuse code fragments throughout a project or across projects. For example, you may have a coding standard where all new classes should contain a base set of operations (constructors, destructor, etc.) and attributes. Or, you may have a common set of initialization or debug code that you apply to all classes. You can use a code template to capture your pattern and easily apply it to any class in your model. This avoids the error-prone copy/paste/rename process.

Rational Rose Visual C++ will reverse engineer an expression code such as

class Client

{

CList<Supplier, Supplier&> mySupplier

}

Upgrading from a Previous Visual C++ Add-In Release

Upgrading from a Previous Visual C++ Add-In Release

The Rose 2000e Visual C++ Add-In is backward compatible with previous versions of the add-in.

The support for MIDL in Rose 2000e is deeper than in Rose 2000. When you use Code Update Tool or Model Update tool on a model created by Rose 2000, Rose 2000e will automatically add new components stereotyped as <<MIDL>> for existing components that represent MIDL projects. Model classes that are stereotyped <<coclass>> or <<interface>> will be automatically assigned to the <<MIDL>> components.

It is recommended that you use the Model Update tool on your Rose 2000 models before attempting to generate code using Rose 2000e.

The model formats used by the Visual C++ and Classic C++ Add-Ins are not interchangeable. If you want to use the Visual C++ Add-In on models created for use with the Classic C++ Add-In, a model conversion utility is provided as a download on the Rose Product Support page located at www.rational.com/rose/support.

Known Visual C++ Add-In Problems and Limitations

Rational Rose Visual C++ does not support the following code constructs:

Rational Rose Visual C++ does not use the Rose "Path Map" mechanism to resolve Microsoft Visual C++ project file pathnames.

The "Browse" functionality should not be used in a multi-project workspace. There is a defect in Microsoft Visual Studio that can cause the class view information to be locked after using "Browse".

Refer to the online documentation for more detail on the capabilities and limitations.

Visual C++ Add-In Defects Fixed since the Previous Release

Web Modeler Add-In (Overview)

Rational Rose Web Modeler is a new add-in for Rational Rose 2000e. It provides visualization, modeling, and tools for developing web applications.

To support visualizing and modeling N-tier web applications, Rose Web Modeler assigns a set of stereotypes and tagged values to your web artifacts. Unified Modeling Language (UML) extensibility features enable modeling the artifacts required to build a web application. Stereotypes and tagged values represent an extension of UML.

Rose Web Modeler creates a model of your multiple tier web application, using specific web artifacts. It supports the Microsoft Windows DNA 2000 (WinDNA), and IBM E-Business Architecture Framework (EBAF) technologies used to build and deploy e-commerce systems.

To visualize and model N-tier web applications, you select the web artifacts from a directory. Rose parses the web artifacts and creates views to show the static structure using the stereotypes and tagged values implement for visualizing and modeling N-tier web applications. You can use Rose Web Modeler to parse HTML files and forms (.htm and .html files), active server pages (.asp and .asa files), and Java server pages (.jsp files).

Rose Web Modeler creates the following diagrams from your N-tier web application:

• Site Overview diagram
• Dependency view
• Client Composition view
• Submit Response view

You can find additional Web Modeler Add-In release note information at the following location:

Known Web Modeler Add-In Defects and Limitations

Trademark Information

Known Web Modeler Add-In Defects and Limitations

Web Publisher Add-In (Overview)

The Rational Rose Web Publisher Add-In allows you to publish Rational Rose models in html. The Web Publisher Add-In exports your Rose model to HTML (including diagrams) so you can view them using a standard browser such as Microsoft Internet Explorer or Netscape Communicator. The Web Publisher also produces meta tags for use by search engines.

The Web Publisher Add-In release notes describe new features and enhancements, known problems and limitations, and fixed defects since the last release.

You can find Web Publisher Add-In release note information at the following locations:

Trademark Information

New Web Publisher Add-In Features and Enhancements

There are no new features or enhancements for the Rose 2000e version of the Web Publisher Add-In.

Known Web Publisher Add-In Problems and Limitations

Web Publisher Add-In Defects Fixed since the Previous Release

No known defects have been fixed since the previous release.

XML DTD Add-In (Overview)

The Rational Rose XML DTD Add-in provides visualization, modeling, and code generation to create XML document type definitions (DTD) for use in your application. You can reverse engineer an existing XML DTD to visualize a DTD's structure using a Rose class diagram. After modeling an XML DTD, you can use the Syntax Checker to validate you XML DTD. From the valid XML DTD model, you generate code to create a new XML DTD.

In addition to reverse engineering an existing XML DTD, you can model a DTD using Rose class stereotypes for XML elements, element attributes, entities, and notations. By modeling an XML DTD, you can visualize the structure of the document to see which element definitions to change or remove. You can also share your XML DTD model with members of your development team to verify that you have captured the XML document requirements.

An XML DTD syntax checker finds errors in the XML DTD model, allowing you to make corrections before the DTD before is implemented. Use the Generate Code feature to produce an XML DTD that you can test or implement in your environment.

To support mapping XML to UML, Rational Rose extends UML with stereotypes for XML elements, element attribute lists, entities, and notations. Stereotypes also represent XML operator symbols, sequence lists, choice lists, and element and element attribute multiplicity.

Note: DTDElementANY cannot be nested. Use this DTDElement at the root level.

You can find additional XML DTD Add-in release note information in the following location:

Known XML DTD Defects and Limitations

Trademark Information

Known XML DTD Add-In Defects and Limitations

There are currently no known defects or limitations.

Contact information for Rational is available on the Rational web page: http://www.rational.com/. If you wish to contact our technical support staff, please have the following information ready:

• Your name, title, company name, phone number, fax number, and e-mail
• Computer make and model
• Operating system and version number
• Product release number and serial number, if you are an existing customer
• A Case ID number, if you are calling in reference to a reported problem

Please contact the appropriate area for Rational Rose technical support:

• North America Technical Support
• Europe, Middle East, and Africa
• Asia Pacific

StereotypeDisplay Enum

Description

StereotypeDisplay is an enumeration that defines values corresponding to the appearance of stereotypes in diagrams. StereotypeDisplay can be used in the StereotypeDisplay property of the RoseItemView class.

Values

The valid values for the StereotypeDisplay enumeration are:

Note: Rational Rose Automation users may use the value (e.g., rsIconNone) in their methods. Rational Rose Script users must use the integer value (e.g., 0) in their methods.

AddObjectFlow Method (Activity)

Applies To

Activity Class

Description

This method adds an object flow from an activity to an object.

Note: To create a view of your object flow on a diagram, use the Diagram.AddRelationView method

Syntax

Set objObjectFlow = objActivity.AddObjectFlow (objObjectInstance)

DeleteObjectFlow Method (Activity)

Applies To

Activity Class

Description

This method deletes an object flow from an activity.

Syntax

isDeleted = objActivity.DeleteObjectFlow (objObjectFlow)

GetObjectFlows Method (Activity)

Applies To

Activity Class

Description

This method retrieves all the object flows associated with an activity.

Syntax

Set colObjectFlowCollection = objActivity.GetObjectFlows ( )

SaveModel Method (Application)

Applies To

Application Class

Description

This method saves the currently open model and returns a value to indicate whether the save was successful.

Syntax

Set lngResult = objApplication.SaveModel (blnSaveUnits)

See Also

Application.Save method

Application.SaveAs method

GetAssignedUnloadedComponents Method (Class)

Applies To

Class Class

Description

This method returns the fully qualified names of the unloaded components to which a class is assigned.

Syntax

Set colStringCollection = objClass.GetAssignedUnloadedComponents ( )

LinkDiagram Method (NoteView)

Applies To

NoteView Class

Description

This method links a diagram to a note view.

Syntax

objNoteView.LinkDiagram (objDiagram)

GetState Method (ObjectFlow)

Applies To

ObjectFlow Class

Description

This method retrieves the State object associated with an object flow.

Syntax

Set objState = objObjectFlow.GetState ( )

SetState Method (ObjectFlow)

Applies To

ObjectFlow Class

Description

This method associates a State object with an object flow.

Syntax

isSet = objObjectFlow.SetState (objState)

AddObjectFlow Method (ObjectInstance)

Applies To

ObjectInstance Class

Description

This method adds an object flow from an object to an activity.

Syntax

Set objObjectFlow = objObjectInstance.AddObjectFlow (objActivity)

DeleteObjectFlow Method (ObjectInstance)

Applies To

ObjectInstance Class

Description

This method deletes an object flow from an object.

Syntax

isDeleted = objObjectInstance.DeleteObjectFlow (objObjectFlow)

GetObjectFlows Method (ObjectInstance)

Applies To

ObjectInstance Class

Description

This method retrieves all the object flows for an object instance.

Syntax

Set colObjectFlowCollection = objObjectInstance.GetObjectFlows (  )

AddObjectInstanceView Method (StateDiagram)

Applies To

StateDiagram Class

Description

This method adds a view of an object instance to a state diagram.

Syntax

Set objInstanceView = objStateDiagram.AddObjectInstanceView (objObjectInstance)

GetDiagramObjectInstanceViews Method (StateDiagram)

Applies To

StateDiagram Class

Description

This method retrieves the collection of instance views on a state diagram, regardless of object instance the instance view represents. To retrieve the collection of instance views for a particular object instance, regardless of diagram, use the StateDiagram.GetObjectInstanceViews method.

Syntax

Set colInstanceViewCollection = objStateDiagram.GetDiagramObjectInstanceViews ( )

GetObjectInstanceViews Method (StateDiagram)

Applies To

StateDiagram Class

Description

This method retrieves the collection of instance views for an object instance, regardless of which diagrams contain the instance views. To only retrieve the collection of instance views on a particular state diagram, regardless of object instance the instance view represents, use the StateDiagram.GetDiagramObjectInstanceViews method.

Syntax

Set colInstanceViewCollection = objStateDiagram.GetObjectInstanceViews (objObjectInstance)

RemoveObjectInstanceView Method (StateDiagram)

Applies To

StateDiagram Class

Description

This method removes a view of an object instance from a diagram without removing the object instance from the model.

Syntax

isRemoved = objStateDiagram.RemoveObjectInstanceView (objObjectInstanceView)

ObjectInstances Property (StateMachine)

Applies To

StateMachine Class

Description

This property returns the collection of object instances contained in a state machine. To retrieve all object instances from a state machine and all of its child state machines, use the StateMachine.GetAllObjectInstances method.

Note: This property is read-only

Syntax

Set colObjectInstanceCollection = objStateMachine.ObjectInstances

Property Type

ObjectInstanceCollection

AddObjectInstance Method (StateMachine)

Applies To

StateMachine Class

Description

This method creates and adds an object instance to a state machine.

Syntax

Set objObjectInstance = objStateMachine.AddObjectInstance (strName)

DeleteObjectInstance Method (StateMachine)

Applies To

StateMachine Class

Description

This method deletes an object instance from a state machine and from the model. This method also removes all views of the object from the model’s diagrams.

Syntax

isDeleted = objStateMachine.DeleteObjectInstance (objObjectInstance)

GetAllObjectInstances Method (StateMachine)

Applies to

StateMachine Class

Description

This method retrieves all object instances belonging to a state machine and all of its child state machines. To only retrieve the object instances in a particular state machine, without retrieving object instances in child state machines, use the StateMachine.ObjectInstances property.

Syntax

Set colObjectInstanceCollection = objStateMachine.GetAllObjectInstances ( )

OnModifiedModelElement Event

Description of Update

This event has been updated to return the following additional intReason codes:

3 = cardinality changed

4 = aggregation changed

5 = end point changed

6 = type changed

7 = initial value changed

OnModifiedModelElementEx Event

Description

The OnModifiedModelElementEx event is generated in certain cases when a user modifies a model element in Rose. This event differs from the OnModifiedModelElement event in that it returns additional information about the modification.

Assigned Language Changed

Rose sends the OnModifiedModelElementEx event, with the reason indicating a language change, to the language add-in corresponding to the old language, providing the language add-in is registered for OnModifiedModelElementEx. If the old language is "Analysis" (that is, there is no assigned language), Rose sends this event to all non-language add-ins that are registered for it.

Rose also sends the OnModifiedModelElementEx event, with the reason indicating a language change, to the language add-in corresponding to the new language, providing the language add-in is registered for OnModifiedModelElementEx. If the new language is "Analysis", Rose sends this event to all non-language add-ins that are registered for it.

If the language of the item did not change from or to "Analysis", Rose sends the OnModifiedModelElementEx event with the reason indicating a language change, to all non-language add-ins that are registered for it.

Name Changed

Rose sends the OnModifiedModelElementEx event, with the reason indicating a name change, to all non-language add-ins registered for the event.

Warning! Do not modify model elements when you receive the OnModifiedModelElementEx event. Otherwise you will be in an infinite loop and Rose will look like it has stopped functioning.

Warning! Do not display a dialog in response to this event. This keeps Rose hanging until your user dismisses your dialog. This is especially bad if a user modifies several model elements at once—users would have to dismiss your dialog several times.

Warning! Return control to Rose as quickly as possible. One way to do this is to spawn another process then return control to Rose.

Filtering of the OnModifiedModelElementEx event can take place quickly on the add-in side by checking the objItem and intReason parameters. For example, if your add-in is interested only in use case name changes, the add-in can check to see if objItem is a use case. If it is not, simply return. If objItem is a use case, but the value of the intReason parameter is not 1 (for Name Changed), simply return.

We recommend that you only use this event as a way to log changes during a Rose session. Then, when the user saves their model, have your add-in read your log and make changes (for example, code generation). Why wait to execute your add-in’s functionality until the user saves their model? Because saving the model is the point at which the user actually commits to the changes they made during their Rose session. If your add-in takes action sooner and the user changes their mind by closing the model without saving changes, your add-in has to undo everything it did based on those abandoned changes.

Registry and Server Requirements

You do not need to add registry entries to register for this event. To receive this event, however, you must provide an OLE Server that includes a method with the correct signature for this event.

Syntax

OnModifiedModelElementEx (objRoseApp, objItem, intReason, vntInfo)

No return value is necessary.

See Also

OnDeletedModelElement event

OnModifiedModelElement event

OnNewModelElement event

OnDeletedModelElementEx Event

Description

The OnDeletedModelElementEx event is generated whenever a user deletes a model element in Rose.

Warning! Do not delete model elements when you receive the OnDeletedModelElementEx event. Otherwise you will be in an infinite loop and Rose will look like it has stopped functioning.

Warning! Do not display a dialog in response to this event. This keeps Rose hanging until your user dismisses your dialog. This is especially bad if a user deletes several model elements at once—users would have to dismiss your dialog several times.

Warning! Return control to Rose as quickly as possible. One way to do this is to spawn another process, then return control to Rose.

Filtering of the OnDeletedModelElementEx event can take place quickly on the add-in side by checking the objItem parameter. For example, if your add-in is interested only in use cases, the add-in can check to see if objItem is a use case. If it is not, simply return.

Registry and Server Requirements

You do not need to add registry entries to register for this event. To receive this event, however, you must provide an OLE Server that includes a method with the correct signature for this event.

If your add-in registers for OnDeletedModelElement, it receives OnDeletedModelElement.

If your add-in registers for OnDeletedModelElement, it receives OnDeletedModelElement.

If your add-in registers for both OnDeletedModelElement and OnDeletedModelElement, it only receives OnDeletedModelElement.

Syntax

OnDeletedModelElement (objRoseApp, objItem, objParentItem)

No return value is necessary.

See Also

OnDeletedModelElement

OnModifiedModelElement

OnNewModelElement