Umple E094 No Association Found Constraint
User Manual [Previous] [Next]
E094 No Association Found Constraint
Umple semantic error raised when a class does not contain an association as defined by a constraint
Model constraints can be applied to Umple classes to ensure they respect certain properties, as defined in their constraints. This error is raised if an association required by a constraint is not found in the class. The multiplicity can optionally be specified.
Example
//The class A generates the error
//by not containing the required
//association
class A {
[model: A -- B]
}
class B {
}
Load the above code into UmpleOnline
Solution to The Above So the Message No Longer Appears
//The error is not generated
//A contains an association
//fulfilling the requirements
//of the constraint
class A {
0..1 -- *B;
[model: A -- B]
}
class B {
}
Load the above code into UmpleOnline