Issue 5095: Preserving state across reclassification (action-semantics-ftf) Source: NIST (Mr. Conrad Bock, conrad.bock@nist.gov conradb@cme.nist.gov) Nature: Uncategorized Issue Severity: Summary: The description of ReclassifyObjectAction does not specify whether the states of the object's state machines are preserved across reclassification. What if a current state before classification does not exist after reclassification? Are exit actions run? Can reclassification interrupt an RTC step? Resolution: accept Revised Text: Added paragraph before the last paragraph in entry for ReclassifyObjectAction in Read Write Chapter: States are preserved for state machines that are in common before and after the action. New state machines are not started. Removed state machines behave as if the object were deleted. Actions taken: March 29, 2002: received issue December 11, 2002: closed issue Discussion: For state machines that are in common before and after the action, the states are preserved. New state machines are not started. Removed state machines behave as if the object were deleted. End of Annotations:===== Reply-To: From: "Conrad Bock" To: "ActionFTF" Subject: Preserving state across reclassification Date: Thu, 28 Mar 2002 15:46:11 -0800 Message-ID: MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Type: text/plain; charset="iso-8859-1" X-UIDL: @6ad96jM!!O04!!-2W!! Juergen, Could you file this for the Action FTF? Thanks, Conrad Summary: Preserving state across reclassification Text: The description of ReclassifyObjectAction does not specify whether the states of the object's state machines are preserved across reclassification. What if a current state before classification does not exist after reclassification? Are exit actions run? Can reclassification interrupt an RTC step?