Issue 4399: CWM Object resource package does not provide support for exceptions (cwm-rtf)
Source: Unisys (Dr. Doug Tolbert, dtolbert408(at)gmail.com)
Nature: Enhancement
Severity: Significant
Summary: Modern object-oriented programming languages such as Java and C#
support the notion of exceptions as first class objects.  However, the CWM
Object resource package does not provide support for exceptions.  Although
exceptions might be added to extension packages specifically designed for
each language that needs them, such an approach would not promote
interchange of exceptions between data warehouse components written in
different languages.  This problem will become particularly accute for .NET
languages in which particular exceptions are defined by language independent
components (such as the .NET CLR libraries) and can be returned to
application components written in any of a group of languages.  Suggested
approaches to resolving this difficulty might include (1) adding exceptions
to the CWM Behavioral package or (2) creating an Object package and placing
the new exception classes in it.
Resolution: 
Revised Text: 
Actions taken:
July 18, 2001: received issue
Discussion: 

End of Annotations:=====
From: "Tolbert, Doug M" <Doug.Tolbert@unisys.com>
To: issues@omg.org
Subject: New Issue for CWM Revision Task Force discussion list
Date: Wed, 18 Jul 2001 16:00:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	      charset="iso-8859-1"
X-UIDL: _<gd933'!!<37!!p-*e9

Source: Unisys Corp. (Doug Tolbert, doug.tolbert@unisys.com)
Nature: Extension
Severity: Significant
Summary: Modern object-oriented programming languages such as Java and
C#
support the notion of exceptions as first class objects.  However, the
CWM
Object resource package does not provide support for exceptions.
Although
exceptions might be added to extension packages specifically designed
for
each language that needs them, such an approach would not promote
interchange of exceptions between data warehouse components written in
different languages.  This problem will become particularly accute for
.NET
languages in which particular exceptions are defined by language
independent
components (such as the .NET CLR libraries) and can be returned to
application components written in any of a group of languages.
Suggested
approaches to resolving this difficulty might include (1) adding
exceptions
to the CWM Behavioral package or (2) creating an Object package and
placing
the new exception classes in it.
Resolution: 
Revised Text: 
Actions taken:
April 3, 2001: received issue