Issue 14531: Problems with OCL for AcceptEventAction::fUML_active_context (fuml-ftf) Source: Model Driven Solutions (Mr. Ed Seidewitz, ed-s(at)modeldriven.com) Nature: Uncategorized Issue Severity: Summary: Specification: Semantics of a Foundational Subset for Executable UML Models (ptc/2008-11-03) Subclause: 7.5.4.2.2 AcceptEventAction The OCL for constraint [1] of AcceptEventAction (fUML_active_context) uses “self.activity” to get the activity for the accept event action. However, the activity property of an action is only non-empty if the action is directly owned by the activity, not nested in a structured activity node. Also, the OCL uses the getContext() operation, which does not seem to be defined in the UML Superstructure or the fUML specification. Resolution: Note that the subclause for AcceptEventAction is actually 7.5.4.2.1. Action has an attribute "context" that gives "the classifier that owns the behavior of which this action is a part". This should be used instead of the "getContext()" operation. Revised Text: In Subclause 7.5.4.2.1 AcceptEventAction, change the OCL for constraint [1] fUML_active_context to: self.context.oclAsType(Class).isActive Actions taken: October 6, 2009: received issue July 23, 2010: closed issue Discussion: End of Annotations:===== ubject: Problems with OCL for AcceptEventAction::fUML_active_context Date: Tue, 6 Oct 2009 19:27:58 -0400 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Problems with OCL for AcceptEventAction::fUML_active_context thread-index: AcpG3KNxZo3CpVi6TcakZhafr9hqYg== From: "Ed Seidewitz" To: Specification: Semantics of a Foundational Subset for Executable UML Models (ptc/2008-11-03) Subclause: 7.5.4.2.2 AcceptEventAction The OCL for constraint [1] of AcceptEventAction (fUML_active_context) uses .self.activity. to get the activity for the accept event action. However, the activity property of an action is only non-empty if the action is directly owned by the activity, not nested in a structured activity node. Also, the OCL uses the getContext() operation, which does not seem to be defined in the UML Superstructure or the fUML specification.