Issue 18753:  Behavior after exceptions are encountered (uml25-ftf)
Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org)
Nature: Uncategorized Issue
Severity: 
Summary: In the discussion of OpaqueBehaviors in caluse 13, it is mentioned that a Behavior may be "abandoned" after it has raised an exception. The semantics of "abandonment" following exceptions are not defined, except (it seems) for the specific case of ExecutableNodes in activities. 

So, is there something general that we can say in Common Behaviors about the state of a Behavior after it has encountered an exception?  For example, in case of a state machine: is it meaningful for the state machine to handle an exception event after it has encountered an exception? (if so, what state is it in following an exception?)

Resolution: 
Revised Text: 
Actions taken:
June 4, 2013: received issue
Discussion: 

End of Annotations:=====
M-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:from:date:x-google-sender-auth:message-id
         :subject:to:cc:content-type;
        bh=fCQzdcTOUgM98SxlKlFvb8RseRHfzMukkdoZZx1kIwo=;
        b=lUklpsUVz3diZg9iiOYH7yJqIb3d5iwjHDYgie2kpvd3ANU8SZNQX89oF80pCdHUSj
         0fDjH86fsbZsgXOuPimGKmneGBHs/H3w/KqXNzOnx6vwA1eFQ4pgvDtAmJVKP76rJk5K
         BHKoyVo3wW6s+hXfq5rfGcEDSa77zKybItjI+yyqj/Nz9f+6Jox4dGr6k/WlGi6qdrq1
         VlaQbTXiRATEalMGGc7Ka6HARnjG3zWC3vPBFJoWcUWu79FyDIf+KyfE2OU05yXrSloH
         h0GoNzvHAwbmfaF3fFohbLnuWm379zYCUcmlm8IZta8Oy7HWggbb3yJxfJv7IUUhbAAZ
         rIUA==
X-Received: by 10.58.15.193 with SMTP id z1mr19327424vec.40.1370367586785;
 Tue, 04 Jun 2013 10:39:46 -0700 (PDT)
Sender: bran.selic@gmail.com
From: Bran Selic <selic@acm.org>
Date: Tue, 4 Jun 2013 13:39:06 -0400
X-Google-Sender-Auth: DqMqz3_zB22txTrbAAYyYRdoJRc
Subject: Three UML 2.5 issues
To: "issues@omg.org" <issues@omg.org>
Cc: "uml25-ftf@omg.org" <uml25-ftf@omg.org>
X-Virus-Scanned: amavisd-new at omg.org


This message contains three separate issues related to UML 2.5 Common Behaviors:

Behavior after exceptions are encountered


In the discussion of OpaqueBehaviors in caluse 13, it is mentioned that a Behavior may be "abandoned" after it has raised an exception. The semantics of "abandonment" following exceptions are not defined, except (it seems) for the specific case of ExecutableNodes in activities. 

So, is there something general that we can say in Common Behaviors about the state of a Behavior after it has encountered an exception?  For example, in case of a state machine: is it meaningful for the state machine to handle an exception event after it has encountered an exception? (if so, what state is it in following an exception?)