Issue 4457: Exceptions do not correspond to common usage (uml2-superstructure-ftf)
Source: NIST (Dr. Conrad Bock, conrad.bock(at)nist.gov)
Nature: Revision
Severity: Significant
Summary:  Exceptions in UML are signals, but the normal usage of the term is
     for non-local flow of control that is trapped in procdural code.
     No signal is normally sent with exceptions.
Resolution: 
Revised Text: 
Actions taken:
August 3, 2001: received issue
March 9, 2005: closed issue
Discussion: 
Closed, no change
The Exception metaclass no longer exists in UML 2.
End of Annotations:=====
Reply-To: <conrad.bock@kabira.com>
From: "Conrad Bock" <conrad.bock@kabira.com>
To: <issues@omg.org>
Cc: "Cris Kobryn" <ckobryn@acm.org>
Subject: UML 1.5 issues
Date: Fri, 3 Aug 2001 08:57:48 -0700
Message-ID: <NDBBJCCGLKIFNFMGDBHNMECNDHAA.conrad.bock@kabira.com>
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)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: Q?+e9Oe%!!h^(!!~DRd9


Juergen,

Here are my issues for UML 1.5.  These are submitted as comments on
the
UML 1.4 as specified in ad/2001-02-13.

Thanks,

Conrad



12) Exceptions do not correspond to common usage

     Exceptions in UML are signals, but the normal usage of the term
     is
     for non-local flow of control that is trapped in procdural code.
     No signal is normally sent with exceptions.

     Nature: Revision
     Severity: Medium