| Element | Change |
|---|---|
| Constructors and operations |
|
| State actions | Modify state actions (transition, entry, exit, and reactions in state) between the delimiters. |
| State-action actions | Modify the state-action actions (in activity diagrams) between the delimiters. |
| Static attributes | Add or modify (but not remove) the initial value. |
IBM® Rational® Rhapsody® roundtrips the first occurrence of the action code. If two or more occurrences are modified, the first modified occurrence is roundtripped. One technique is to call an operation in state, state action, and transition actions, eliminating duplication of the action code and possible roundtrip ambiguity.
The following table lists the modifications that can be roundtripped in a class specification file.
| Element | Change |
|---|---|
| Arguments | Add, remove, and change the type of constructors, operations,
and triggered operation arguments. Changes to argument descriptions in the class specification file are not roundtripped. |
| Association | Add or remove association, directed association, or aggregation. You must set the CPP_ or JAVA_Roundtrip::Update::AcceptChanges property to the All value. |
| Attributes |
|
| Classes |
|
| Constructors and operations |
|
| Destructors | Modify the descriptions. If there is a blank line at the end of the description, the description is lost. |
| Nested classes | Add, remove, or modify a nested class. |
| Relations |
|
| Standard operations | Modify standard operations to inline, by adding "inline" to the declaration. The definition is generated automatically. The <lang>_CG::Operation::Inline property is set to in_source. As a result, the implementation of the function stays in the implementation file. (The "inline" keyword is added to both, specification and implementation files.) |
| Triggered operations | Modify the descriptions. If there is a blank line at the end of the description, the description is lost. |
| User-defined types | Add, remove, or modify user-defined types. |