Issue 2392:   ExchangeRateValue init interface need information                                                                                                                                                     (currency-rtf)
Source:  (, )
Nature:  Revision
Severity: 
Summary: Summary: The init() interface appears in the consolidated IDL Specifications portion
 of the document, but does not appear and is not documented or discussed in
 section 2.3.8.
 

Resolution: resolved by Currency 2 RTF
Revised Text: Resolution: Add text to document to describe the init method.	
Revised Text: At the beginning of section 2.3.8, after value ExchangeRate add the following:
Initialization
void init(in wstring rateTypeID, 
in wstring sourceCurrencyMnemonic, 
in wstring targetCurrencyMnemonic, 
in CBO::DDecimal conversionFactor, 
in CBO::DTime beginDateTime, in CBO::DTime endDateTime) raises(FbcException);

Initializes the ExchangeRate object with the attributes passed.  Note that all values must meet the preconditions associated with each parameter passed.  See the accessors below for their specific preconditions.

Actions taken:
February 2, 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: ExchangeRateValue init interface need information
Issue Type: Text Revision
Issue Description:
The init() interface appears in the consolidated IDL Specifications
portion
of the document, but does not appear and is not documented or
discussed in
section 2.3.8.

Date: Wed, 1 Nov 2000 10:57:17 -0800
From: Blake Biesecker <blakeb@gemstone.com>
To: ots-rtf@omg.org
Subject: Issue 2392 - non-transactional objects
Message-ID: <20001101105717.A22222@gemstone.com>
Mime-Version: 1.0
X-Mailer: Mutt 1.0pre4i
X-Disclaimer: I only speak for myself, unless I expressly indicate
otherwise.
Content-Type: text/plain; charset=us-ascii
X-UIDL: c0n!!C^Ge9bO~e9I9[d9

Does anyone think this issue was not resolved by
3425:

Issue 2932: ots-rtf: non-transactional objects (ots-rtf)

Click here for this issue's archive.
Source: Object Oriented Concepts (Mr. Michi Henning, michi@ooc.com.au)
Nature: Uncategorized Issue
Severity: 
Summary: The spec says that a transactional object can call into a
non-transactional one (page 10-5). Fine. But it never says what should
happen in such a case. 
Resolution: 
Revised Text: 
Actions taken:
October 11, 1999: received issue

Blake