Operation bodyCondition has to have a boolean value

[eclipse-ocl-bot]

| --- | --- |
| Bugzilla Link | 116251 |
| Status | CLOSED FIXED |
| Importance | P2 major |
| Reported | Nov 14, 2005 11:04 EDT |
| Modified | May 27, 2011 02:42 EDT |
| Version | 1.0.0 |
| Reporter | Vishy Ramaswamy |

Description

OCL framework assumes the bodyCondition constraint applies to the result of
the operation and does not allow the constraint to include result =
. This is incorrect as with result =, the bodyCondition
constraint is not a valid constraint since it does not result in a boolean
value.

The bodyCondition should be a valid constraint just like a postCondition. From
the UML2 specification: "The bodyCondition for an operation constrains the
return result. The bodyCondition differs from postconditions in that the
bodyCondition may be overridden when an operation is redefined, whereas
postconditions can only be added during redefinition.". So the framework
should not assume result = is part of the constraint.

[eclipse-ocl-bot]

By Christian Damus on Dec 14, 2005 17:46

Committed the fix.

The OCL parser is updated to require all operation constraints to be boolean valued and, furthermore, that body conditions look like:
o result = OR
o = result OR
o let ... in result = OR
o let ... in = result OR
o let ... in let ... in result = ETC.

where is an expression conforming to the operation's return type and does not reference the special result variable.

[eclipse-ocl-bot]

By Nick Boldt on Jan 28, 2008 16:34

Move to verified as per bug 206558.

[eclipse-ocl-bot]

By Ed Willink on May 27, 2011 02:40

Closing after over a year in verified state.

[eclipse-ocl-bot]

By Ed Willink on May 27, 2011 02:42

Closing after over a year in verified state.