Issue 2394: Legal value ranges for numerics in ExchangeRateValue should be discussed (currency-rtf) Source: (, ) Nature: Revision Severity: Summary: Summary: Can conversionFactor represent a value <= 0.0? I would think not. An exception should be thrown if the conversion factor is attempted to be set with a Ddecimal that represents a value <= 0.0 The beginDateTime must be < endDateTime in the init() call correct? Throw an exception if this is not the case. The source and target currency mnemonics cannot be the same in the init() call correct? Throw an exception if they are. Resolution: Closed, no change. This issue is fixed by Issue 2393 Revised Text: Actions taken: January 11, 1999: received issue May 4, 2000: closed issue Discussion: End of Annotations:===== Return-Path: 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: Legal value ranges for numerics in ExchangeRateValue should be discussed Issue Type: Text Revision Issue Description: Can conversionFactor represent a value <= 0.0? I would think not. An exception should be thrown if the conversion factor is attempted to be set with a Ddecimal that represents a value <= 0.0 The beginDateTime must be < endDateTime in the init() call correct? Throw an exception if this is not the case. The source and target currency mnemonics cannot be the same in the init() call correct? Throw an exception if they are.