Issue 17502: Specification of ClassifierBehaviorExecution and ObjectActivation are not consistent with Annex A (fuml-rtf) 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 (fUML), v1.0 (formal/2011-02-02) Subclause: 8.4.3.2.1 ClassifierBehaviorExecution, 8.4.3.2.5 ObjectActivation Subclause A.3.7 establishes the Java notation “_startObjectBehavior();” as mapping to a start object behavior action, not an operation call, and it also states that “A class may not define a user operation called ‘_startObjectBehavior.’” However, in Subclause 8.4.3.1, Figure 8.17, _startObjectBehavior is shown as an operation on both ClassifierBehaviorExecution and ObjectActivation, and it is specified in as an operation for these classes in Subclauses 8.4.3.2.1 and 8.4.3.2.5. Subclause A.3.8 establishes the Java notation “_send(new <signal>());” as mapping to a send signal action, not an operation call. However, in Figure 8.17, _send is shown as an operation of ObjectActivation, and it is specified as an operation in Subclause 8.4.3.2.5. Resolution: Revised Text: Actions taken: July 16, 2012: received issue Discussion: End of Annotations:===== m: Ed Seidewitz To: "Juergen Boldt (juergen@omg.org)" Date: Mon, 16 Jul 2012 16:06:04 -0400 Subject: Could you do me a favor? RE: Specification of ClassifierBehaviorExecution and ObjectActivation are not consistent with Annex A Thread-Topic: Could you do me a favor? RE: Specification of ClassifierBehaviorExecution and ObjectActivation are not consistent with Annex A Thread-Index: Ac1jjjl3HKSEWafST8aY2RLk9Kd78Q== Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Mailprotector-Decision: deliver X-Mailprotector-Connection: TLSv1|[10.1.50.225]|10.1.50.225|outbound.mailprotector.net|0|0|0|new|ugly|0|0|0|0 X-Mailprotector-Results: null_ptr subject_50_chars subject_10_spaces clean X-Mailprotector-Score: 80 X-Mailprotector-IP-Analysis: 0, 10.1.50.225, Ugly c=0 p=0 Source New X-Mailprotector-Scan-Diagnostics: 0-0-0-10021-c X-Mailprotector-ID: 8d8203a2-3180-458a-889c-1a8ab869ab8c Juergen . Could I possibly get an issue number today for the issue below? I wanted to send out another fUML RTF ballot today, including a resolution to this issue, but then I realized I had forgotten to actually submit the issue! Thanks. -- Ed From: Ed Seidewitz Sent: Monday, July 16, 2012 11:37 AM To: issues@omg.org Subject: Specification of ClassifierBehaviorExecution and ObjectActivation are not consistent with Annex A Specification: Semantics of a Foundational Subset for Executable UML Models (fUML), v1.0 (formal/2011-02-02) Subclause: 8.4.3.2.1 ClassifierBehaviorExecution, 8.4.3.2.5 ObjectActivation Subclause A.3.7 establishes the Java notation ._startObjectBehavior();. as mapping to a start object behavior action, not an operation call, and it also states that .A class may not define a user operation called ._startObjectBehavior... However, in Subclause 8.4.3.1, Figure 8.17, _startObjectBehavior is shown as an operation on both ClassifierBehaviorExecution and ObjectActivation, and it is specified in as an operation for these classes in Subclauses 8.4.3.2.1 and 8.4.3.2.5. Subclause A.3.8 establishes the Java notation ._send(new ());. as mapping to a send signal action, not an operation call. However, in Figure 8.17, _send is shown as an operation of ObjectActivation, and it is specified as an operation in Subclause 8.4.3.2.5.