Issue 13312: Issue: ObjectNodeActivation::offeredTokenCount is not initialized (fuml-ftf) Source: Model Driven Solutions (Mr. Ed Seidewitz, ed-s(at)modeldriven.com) Nature: Uncategorized Issue Severity: Summary: Specification: Semantics of a Foundation Subset for Executable UML Models, FTF – Beta 1 (ptc/08-11-03) Section: 8.5.2.2.15 (ObjectNodeActivation) Summary: The ObjectNodeActivation::offeredTokenCount attribute is never initialized. This is not a problem for Java execution, since Java semantics initializes integer variables to zero by default. But this is not correct per UML execution semantics. Proposed resolution: Add an ObjectNodeActivation::run() operation that overrides the inherited operation with the following body: super.run(); this.offeredTokenCount = 0; Resolution: Change the code as proposed Revised Text: Add an ObjectNodeActivation::run() operation that overrides the inherited operation with the following body: super.run(); this.offeredTokenCount = 0; Actions taken: January 20, 2009: received issue July 23, 2010: closed issue Discussion: End of Annotations:===== ubject: Issue: ObjectNodeActivation::offeredTokenCount is not initialized Date: Tue, 20 Jan 2009 15:26:12 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issue: ObjectNodeActivation::offeredTokenCount is not initialized thread-index: Acl7PVWl1J7QWrcqRpCQH6YwbsnHAg== From: "Ed Seidewitz" To: Cc: Specification: Semantics of a Foundation Subset for Executable UML Models, FTF . Beta 1 (ptc/08-11-03) Section: 8.5.2.2.15 (ObjectNodeActivation) Summary: The ObjectNodeActivation::offeredTokenCount attribute is never initialized. This is not a problem for Java execution, since Java semantics initializes integer variables to zero by default. But this is not correct per UML execution semantics. Proposed resolution: Add an ObjectNodeActivation::run() operation that overrides the inherited operation with the following body: super.run(); this.offeredTokenCount = 0;