Issue 2366:  Extend ExceptionType enumerations                                                                                                                                                                      (currency-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: Need to add some additional enumerations to the ExceptionType enumeration.
 Some of the suggestions are the following : INVALID_VALUE,
 INVALID_STATE_IDENTIFIER, INVALID_DATE_RANGE, INVALID_CONVERSION_FACTOR,
 INVALID_STRING (when a provided string is empty or contains only white
 space), UNINITIALIZED_DATA, DATE_RANGE_FRAGMENTATION (when adding an
 exchange rate whose effective window in time would fragment existing
 exchange rates), INVALID_MULTIPLIER, INVALID_DIVISOR, STATE_IDS_EXHAUSTED.
 (Our implementation plan is such that INVALID_ROUNDING_DIGIT,
 INVALID_MULTIPLIER, etc. should really be discarded in favor of using
 INVALID_VALUE. Where an explicit value has already been specified in the
 submission (e.g. INVALID_ROUNDING_DIGIT) we will use it but hope for our
 recommendation to be heeded. For exception types that are necessary but
 were not included in the adopted submission, we will add our own (e.g.
 INVALID_STATE_IDENTIFIER, INVALID_VALUE) and use whenever necessary.
 
 

Resolution: resolved in Currency 2 RTF, closed
Revised Text: :  Incorporate changes to text and idl for INVALID_VALUE, UNINITIALIZED_DATA and DATABASE_EXCEPTION. 
Also See Issue 2363 for INVALID_STATE_IDENTIFIER
The other suggested exception types will not be added since INVALID_VALUE can suffice.

Revised Text: In section 2.3.5 and Appendix A.1 add the following Exception types to the enum ExceptionType:

INVALID_VALUE. 
UNINITIALIZED_DATA,
DATABASE_EXCEPTION
Revised IDL: add the following Exception type to the enum ExceptionType:
INVALID_VALUE. 
UNINITIALIZED_DATA,
DATABASE_EXCEPTION


Actions taken:
January 11, 1999: received issue
May 4, 2000: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <Robert_Mickley@CYBORG.COM>
From: Robert_Mickley@CYBORG.COM
X-Lotus-FromDomain: CYBORG@CYBORG_NET
To: issues@omg.org
cc: Robert_Mickley@CYBORG.COM, Amy_Griffis@CYBORG.COM
Date: Mon, 11 Jan 1999 21:28:52 -0700
Subject: Currency RTF Issues
Content-Disposition: inline



Today is the deadline for comments for the Currency RTF.  Below is an
itemized list of additions to that list.



Issue Title:  Extend ExceptionType enumerations
Issue Type: IDL Revision
Issue Description:
Need to add some additional enumerations to the ExceptionType
enumeration.
Some of the suggestions are the following : INVALID_VALUE,
INVALID_STATE_IDENTIFIER, INVALID_DATE_RANGE,
INVALID_CONVERSION_FACTOR,
INVALID_STRING (when a provided string is empty or contains only white
space), UNINITIALIZED_DATA, DATE_RANGE_FRAGMENTATION (when adding an
exchange rate whose effective window in time would fragment existing
exchange rates), INVALID_MULTIPLIER, INVALID_DIVISOR,
STATE_IDS_EXHAUSTED.
(Our implementation plan is such that INVALID_ROUNDING_DIGIT,
INVALID_MULTIPLIER, etc. should really be discarded in favor of using
INVALID_VALUE. Where an explicit value has already been specified in
the
submission (e.g. INVALID_ROUNDING_DIGIT) we will use it but hope for
our
recommendation to be heeded. For exception types that are necessary
but
were not included in the adopted submission, we will add our own (e.g.
INVALID_STATE_IDENTIFIER, INVALID_VALUE) and use whenever necessary.