User Manual Basics

Comments and Requirements

Classes and Interfaces

Aspect Orientation

Mixsets and Filters

Generation Templates

Composite Structure

Grammar To Define Umple

Errors and Warnings 1-50

Errors and Warnings 51-99

E051 Event Parameters Must Match

E052 State Machine Name Clash

E053 No Concurrency At Top Level

W054 Duplicate Events

W055 Duplicate Events Within Substates

W056 No Events in Queued State Machine

W057 No Events in Pooled State Machine

E058 Regular Queued and Pooled State Machines in Class

E059 Queued and Pooled State Machines in Class

E060 Pooled and Regular State Machines in Class

E061 Queued and Regular State Machines in Class

W062 Unspecified Event in Pooled State Machine

E063 Reserved Name History State

E064 Non Existent History State

E065 No Substates History State

W066 Transition Multiple Possible Destinations

W067 Non Reachable State

W068 Destination State Not Found

W069 Auto Transition Conflict

W071 Duplicate Method Different Type

W072 Refactored Final State

E073 Duplicate Parallel State Machine Name

E074 User Defined State Cannot be Named Final

E075 UserDefinedStateMachineCannotBeNamedTimer

E080 Invalid Abstract Class Association

E081 Invalid Multivalued Attribute Assignment

W082 Conflicting Method Modifiers

E083 Invalid Multivalued Attribute Initialization

W089 Association Rolename Matching Classname

E090 Attribute Name Not Found Constraint

E091 Attribute Of Type Not Found Constraint

E092 Class Is Not Subclass Constraint

E093 Class Is Not Superclass Constraint

E094 No Association Found Constraint

E095 Duplicate Enumerations

E096 Enumeration Naming Conflict

E097 Enumeration and State Machine Conflict

Errors and Warnings 100-999

Errors and Warnings 1000+

Runtime Exceptions

Combined Version

[Previous] [Next]

list of dots

User Manual [Previous] [Next]

W069 Auto Transition Conflict

Umple semantic warning issued when an auto-transition has a conflict with a previously defined transition

An auto-transition in a state that is declared after another auto-transition will be ignored, and only the first auto-transition will be executed. No warning is issued if the destination state of both auto-transitions is the same.

Example

//The warning is generated due
//to the auto-transition to s2
//conflicting with the auto-
//transition to s3
class A {
sm {
s1 {
entry /{doSomething();}
-> s2;
do {doSomethingElse();}
-> s3;
}
s2 {
}
s3 {
}
}
void doSomething() {}
void doSomethingElse() {}
}

//The warning is generated due
//to the auto-transition to s2
//conflicting with the auto-
//transition to s3
class A {
  sm {
    s1 {
      entry /{doSomething();}
      -> s2;
      
      do {doSomethingElse();}
      -> s3;
    }
    s2 {
    }
    s3 {
    }
  }
  void doSomething() {}
  void doSomethingElse() {}
}

Load the above code into UmpleOnline

Solution to The Above So the Message No Longer Appears

//The warning is avoided here
//by keeping only one auto-
//transition
class A {
sm {
s1 {
entry /{doSomething();}
do {doSomethingElse();}
-> s2;
}
s2 {
}
}
void doSomething() {}
void doSomethingElse() {}
}

//The warning is avoided here
//by keeping only one auto-
//transition
class A {
  sm {
    s1 {
      entry /{doSomething();}
      do {doSomethingElse();}
      -> s2;
    }
    s2 {
    }
  }
  void doSomething() {}
  void doSomethingElse() {}
}

Load the above code into UmpleOnline