${taskforce.name} Avatar
  1. OMG Task Force

Currency RTF 2 — All Issues

  • Key: CURR11
  • Issues Count: 76
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
CURR11-47 ExchangeRateValue init interface need information CURR 1.0 CURR 1.1 Resolved closed
CURR11-46 IDL Changes to support date ranges on ExchangeRateValue CURR 1.0 CURR 1.1 Resolved closed
CURR11-58 Correct interface symantics for createExchangeRate CURR 1.0 CURR 1.1 Resolved closed
CURR11-57 Correct Currency create method CURR 1.0 CURR 1.1 Resolved closed
CURR11-52 Change the name of getStateIdentifier to issueStateIdentifier CURR 1.0 CURR 1.1 Resolved closed
CURR11-51 Correct issues with CosObjectIdentity::IdentifiableObject in StateIDManage CURR 1.0 CURR 1.1 Resolved closed
CURR11-50 Clarification on whether stateID manages session or state access CURR 1.0 CURR 1.1 Resolved closed
CURR11-49 Legal value ranges for numerics in ExchangeRateValue should be discussed CURR 1.0 CURR 1.1 Resolved closed
CURR11-53 Add validity checkign for StateIdentifier CURR 1.0 CURR 1.1 Resolved closed
CURR11-54 what values are used to determine if a currency exists in CurrencyBook CURR 1.0 CURR 1.1 Resolved closed
CURR11-55 Clarify the areEquivelent interface of the CurrencyBook CURR 1.0 CURR 1.1 Resolved closed
CURR11-48 Missing details on preconditions on the ExchangeRateValue CURR 1.0 CURR 1.1 Resolved closed
CURR11-56 Change get Currency to retrieveCurrency CURR 1.0 CURR 1.1 Resolved closed
CURR11-42 Add description of isCurrency Active CURR 1.0 CURR 1.1 Resolved closed
CURR11-44 MoneyValue init interface need information CURR 1.0 CURR 1.1 Resolved closed
CURR11-43 Add mechanism to create Money instances for moneyValue CURR 1.0 CURR 1.1 Resolved closed
CURR11-45 exception semantics for MoneyValue CURR 1.0 CURR 1.1 Resolved closed
CURR11-74 Supplied Data for ISO Locales in MoneyFormatter needs to be discussed CURR 1.0 CURR 1.1 Resolved closed
CURR11-73 Change name of CBO::DAmountOfTime interface to CBO::AmountOfTime CURR 1.0 CURR 1.1 Resolved closed
CURR11-76 Value types need state CURR 1.0 CURR 1.1 Resolved closed
CURR11-75 Add clarification on formatting string in MoneyFormatter CURR 1.0 CURR 1.1 Resolved closed
CURR11-64 Clarify legal values for the MoneyFormatter format strings CURR 1.0 CURR 1.1 Resolved closed
CURR11-61 removeExchangeRate() interface issue CURR 1.0 CURR 1.1 Resolved closed
CURR11-60 Modify and specify the behavior of the insertExchangeRate interface CURR 1.0 CURR 1.1 Resolved closed
CURR11-69 Create mechanism to modify what negative prefix is for formatting string CURR 1.0 CURR 1.1 Resolved closed
CURR11-66 Clarify exceptions for setFormattingString in MoneyFormatter CURR 1.0 CURR 1.1 Resolved closed
CURR11-65 Clarify contradiction betw setFormatByLocale & setFormattingString CURR 1.0 CURR 1.1 Resolved closed
CURR11-68 Interface changes for MoneyFormatter pattern handling CURR 1.0 CURR 1.1 Resolved closed
CURR11-67 Typo on SetPatternMnemonicSymbol name CURR 1.0 CURR 1.1 Resolved closed
CURR11-71 Add interfaces for internal precision on MoneyCalculator CURR 1.0 CURR 1.1 Resolved closed
CURR11-70 Clarify on comparison methods of the MoneyCalculator CURR 1.0 CURR 1.1 Resolved closed
CURR11-63 Clarify MoneyFormatter use of the # symbol CURR 1.0 CURR 1.1 Resolved closed
CURR11-62 Proposed interface changes to ExchangeRateManager CURR 1.0 CURR 1.1 Resolved closed
CURR11-72 Fix omitted precondition for MoneyCalculator CURR 1.0 CURR 1.1 Resolved closed
CURR11-59 Change the name of addExchangeRate to insertExchangeRate CURR 1.0 CURR 1.1 Resolved closed
CURR11-34 Exchange rates need to be date based. CURR 1.0 CURR 1.1 Resolved closed
CURR11-33 Clearer information describing different rounding types is needed CURR 1.0 CURR 1.1 Resolved closed
CURR11-32 Text indicating that vendors shall provide default values CURR 1.0 CURR 1.1 Resolved closed
CURR11-31 Extend ExceptionType enumerations CURR 1.0 CURR 1.1 Resolved closed
CURR11-36 Propose modification to the init method of CurrencyValue CURR 1.0 CURR 1.1 Resolved closed
CURR11-35 vendor implementations can implement only parts and interoperate-Statement CURR 1.0 CURR 1.1 Resolved closed
CURR11-39 More clarification on the semantics of string arguements for CurrencyValue CURR 1.0 CURR 1.1 Resolved closed
CURR11-38 Missing details on preconditions on the Currency interface as a whole CURR 1.0 CURR 1.1 Resolved closed
CURR11-41 Typos in CurrencyValue section CURR 1.0 CURR 1.1 Resolved closed
CURR11-40 Legal value ranges for numerics in CurrencyValue init should be discussed CURR 1.0 CURR 1.1 Resolved closed
CURR11-37 missing description on the init method for CurrencyValue CURR 1.0 CURR 1.1 Resolved closed
CURR11-30 StateID Exception CURR 1.0 CURR 1.1 Resolved closed
CURR11-29 Change double to short for internal precision CURR 1.0 CURR 1.1 Resolved closed
CURR11-28 Add idl and text to describe the getAllExchangeRates method CURR 1.0 CURR 1.1 Resolved closed
CURR11-27 Add text for formatter that the format string will be used for parsing CURR 1.0 CURR 1.1 Resolved closed
CURR11-26 Change text description of behavior of ROUND_FLOOR and ROUND_CEILING CURR 1.0 CURR 1.1 Resolved closed
CURR11-25 Clarify on comparison methods of the calculato CURR 1.0 CURR 1.1 Resolved closed
CURR11-24 clarification on how the "#" is used in the money formatter CURR 1.0 CURR 1.1 Resolved closed
CURR11-21 Place maximums on wstrings for interoperability CURR 1.0 open
CURR11-15 Add interfaces to DTime properly handle the DAmountOfTime difference inter CURR 1.0 open
CURR11-17 Improve text in specification of of DAmountOfTime CURR 1.0 open
CURR11-16 Support millisecond precision in DAmountOfTime CURR 1.0 open
CURR11-20 Changing RoundType.DONT_ROUND CURR 1.0 open
CURR11-19 Add ability to clone Money CURR 1.0 open
CURR11-23 Remove Depedence in FBCCurrency of CBO::DDecimal CURR 1.0 open
CURR11-22 Remove Dependence in FBCCurrency of CBO::DTime CURR 1.0 open
CURR11-18 Remove dependence on a specific version of the ISO 4217 standard CURR 1.0 open
CURR11-8 : Change name of interface to CBO::Decima CURR 1.0 open
CURR11-7 Corrections to the equals/setEquals interfaces of DTime CURR 1.0 open
CURR11-6 Improve DTime exception handling CURR 1.0 open
CURR11-14 Add interface to DTime CURR 1.0 open
CURR11-13 Clarification required on setYear of the DTime interface CURR 1.0 open
CURR11-12 support to set precision to something other than milliseconds CURR 1.0 open
CURR11-5 describe how the individual components should be accessed CURR 1.0 open
CURR11-4 Description of Exception handling semantics CURR 1.0 open
CURR11-3 Add text for DTime and DDecimal from CBO submission into Currency spec. CURR 1.0 open
CURR11-11 : Change name of interface to CBO::Time CURR 1.0 open
CURR11-10 Add interfaces to DDecimal CURR 1.0 open
CURR11-9 Clarify the equality method of DDecimal CURR 1.0 open
CURR11-2 The idl for CBO::DTime needs the method: long getYear() CURR 1.0 open
CURR11-1 Clairfy comparisons of two CBO::Ddecimal values on equality CURR 1.0 open

Issues Descriptions

ExchangeRateValue init interface need information

  • Key: CURR11-47
  • Legacy Issue Number: 2392
  • Status: closed  
  • Source: Anonymous
  • 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.

  • Reported: CURR 1.0 — Tue, 2 Feb 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

IDL Changes to support date ranges on ExchangeRateValue

  • Key: CURR11-46
  • Legacy Issue Number: 2391
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Propose the addition of the following interface(s):

    void setDateRange(in CBO::Dtime beginDateTime,
    in CBO::Dtime endDateTime) – Sets the window in
    time over which the ExchangeRate instance is valid.
    CBO::Dtime getStartDate() – Returns the date and time at which
    the ExchangeRate took effect.
    CBO::Dtime getEndDate() – Returns the date and time at which the
    ExchangeRate is no longer valid.

    Will also need an appropriate exception to throw when the date
    range is attempted to be set and beginDateTime >= endDateTime. Do
    not think that the beginDateTime should be allowed to be equal to
    the endDateTime as that then means that the ExchangeRate is valid
    for zero seconds.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Correct interface symantics for createExchangeRate

  • Key: CURR11-58
  • Legacy Issue Number: 2403
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The createExchangeRate() and getExchangeRate() interfaces accept arguments
    sourceCurrencyMnemonic and targetCurrencyMnemonic. There is no mention in
    the document regarding how the component should react (e.g. throw an
    exception) if the passed arguments are the same mnemonic.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed issue, resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Correct Currency create method

  • Key: CURR11-57
  • Legacy Issue Number: 2402
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Currency create(
    in wstring name,
    in wstring fractionName,
    in wstring mnemonic,
    in short numericCode,
    in wstring symbol,
    in wstring fractionSymbol,
    in short ratioOfFractionToWhole,
    in wstring description,
    in CBO::DTime introductionDate,
    in CBO::DTime expirationDate,
    in boolean isISO,
    in wstring ISOVersion,
    in StringCollection locales)

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Change the name of getStateIdentifier to issueStateIdentifier

  • Key: CURR11-52
  • Legacy Issue Number: 2397
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: getStateIdentifier() implies an accessor which it is not. Change name of
    the interface to issueStateIdentifier().

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Correct issues with CosObjectIdentity::IdentifiableObject in StateIDManage

  • Key: CURR11-51
  • Legacy Issue Number: 2396
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Use of CosObjectIdentity::IdentifiableObject as the interface for a
    stateIdentifier. There is a particularly concerning paragraph in v1.0 of
    the Relationship Service regarding the interface: “The value of this
    attribute [readonly attribute ObjectIdentifier constant_random_id] is not
    guaranteed to be unique; that is, another identifiable object can return
    the same value. However, if objects return different identifiers, clients
    can determine that two identifiable objects are not identical”.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed, no changes

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarification on whether stateID manages session or state access

  • Key: CURR11-50
  • Legacy Issue Number: 2395
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: In general the decision needs to be made as to whether a given
    stateIdentifier is used to indicate the boundaries of a session or a simple
    configuration, as it currently seems to attempt to support both. Whichever
    direction is chosen, all of the interfaces that accept a stateIdentifier as
    an argument should be revisited to ensure that the intent of the interface
    is still properly supported. e.g. Should the currency component still offer
    a “connectionless” interface to its consumers?

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed, no action taken

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Legal value ranges for numerics in ExchangeRateValue should be discussed

  • Key: CURR11-49
  • Legacy Issue Number: 2394
  • Status: closed  
  • Source: Anonymous
  • 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.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    Closed, no change. This issue is fixed by Issue 2393

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add validity checkign for StateIdentifier

  • Key: CURR11-53
  • Legacy Issue Number: 2398
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Add the boolean valid(in CosObjectIdentifier::IdentifiableObject
    stateIdentifier) interface. This must be included so that each interface
    that accepts a stateIdentifier can do validity checking against it before
    servicing the request.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed issue, resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

what values are used to determine if a currency exists in CurrencyBook

  • Key: CURR11-54
  • Legacy Issue Number: 2399
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: addCurrency() will raise an exception “if the currency already exists in
    the CurrencyBook …”. There is no mention of what elements of a currency are
    required to determine if one “already exists”. What
    needs to be fully
    detailed are those Currency elements which must be used to determine
    uniqueness. e.g. mnemonic, numeric code, etc.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed, resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarify the areEquivelent interface of the CurrencyBook

  • Key: CURR11-55
  • Legacy Issue Number: 2400
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: areEquivalent() “determines whether the two passed-in Currency objects
    contain the same elements”. Again, what needs to be fully detailed are
    those Currency elements which must be to determine uniqueness. e.g.
    mnemonic, numeric code, etc.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed, resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Missing details on preconditions on the ExchangeRateValue

  • Key: CURR11-48
  • Legacy Issue Number: 2393
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Issue Description: Missing details on preconditions on the
    ExchangeRateValue interface as a whole

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Change get Currency to retrieveCurrency

  • Key: CURR11-56
  • Legacy Issue Number: 2401
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The getCurrency() method name lends the consumer to believe that it is
    simply an accessor method, which it is not. It is a searching method.
    Change the method name to retrieveCurrency() or something that indicates
    searching semantics.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed issue, resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add description of isCurrency Active

  • Key: CURR11-42
  • Legacy Issue Number: 2387
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There is no description of isCurrentlyActive() and when/why it would return
    true vs. false. Since it is described in the same area as the
    introduction/expiration date, does it simply perform a check to see if the
    current system time falls between the introduction and expiration
    date/times?

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed , resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

MoneyValue init interface need information

  • Key: CURR11-44
  • Legacy Issue Number: 2389
  • Status: closed  
  • Source: Anonymous
  • 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.7.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add mechanism to create Money instances for moneyValue

  • Key: CURR11-43
  • Legacy Issue Number: 2388
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Issue Description: There is no mechanism to create Money instances via a
    factory/type manager method.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF, close

  • Updated: Fri, 6 Mar 2015 20:58 GMT

exception semantics for MoneyValue

  • Key: CURR11-45
  • Legacy Issue Number: 2390
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There is no descriptive text stating why an FbcException would be raised
    when calling init(), [gs]etCurrencyMnemonic(), or [gs]etValue().

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Supplied Data for ISO Locales in MoneyFormatter needs to be discussed

  • Key: CURR11-74
  • Legacy Issue Number: 2775
  • Status: closed  
  • Source: Anonymous
  • Summary:

    : Need explanation that the ISO locale and it's associated format data will be provided by the vendor supplying the implementation.

  • Reported: CURR 1.0 — Wed, 30 Jun 1999 04:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Change name of CBO::DAmountOfTime interface to CBO::AmountOfTime

  • Key: CURR11-73
  • Legacy Issue Number: 2428
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Issue Description: Change name of CBO::DAmountOfTime interface to
    CBO::AmountOfTime

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    :AmountOfTime

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Value types need state

  • Key: CURR11-76
  • Legacy Issue Number: 2886
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The value types in FbcCurrency (Currency, Money and ExchangeRate) need
    state added to them as defined by Objects By Value.

  • Reported: CURR 1.0 — Tue, 14 Sep 1999 04:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add clarification on formatting string in MoneyFormatter

  • Key: CURR11-75
  • Legacy Issue Number: 2779
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Need clarification on formatting in MoneyFormatter. Can literal text be added to the formatting string, or is it strictly pattern based? If literal text cannot be added, add text to indicate the formatting string must contain only pattern characters.

  • Reported: CURR 1.0 — Wed, 30 Jun 1999 04:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    Fixed in issue 2409

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarify legal values for the MoneyFormatter format strings

  • Key: CURR11-64
  • Legacy Issue Number: 2409
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Clarify legal values for the MoneyFormatter format strings

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

removeExchangeRate() interface issue

  • Key: CURR11-61
  • Legacy Issue Number: 2406
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The removeExchangeRate() interface may be too heavy handed. Modify
    the semantics of this interface to support making an exchange rate
    instance unsuitable for use (e.g. inactive). In this way, the exchange rate
    instance would still be known to the component, but could no longer be used
    in computations. It could however be extracted for reporting purposes, etc.
    Would need interface accommodations though to indicate the extraction of
    exchange rates that are “inactive”.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    Not an issue

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Modify and specify the behavior of the insertExchangeRate interface

  • Key: CURR11-60
  • Legacy Issue Number: 2405
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The behavior of the insertExchangeRate() interface should be modified.
    Since ExchangeRates will now have a window in time over which they are
    effective, the behavior needs to address what happens when an exchange rate
    is attempted to be inserted that overlaps (in time) an existing exchange
    rate. i.e. Suppose an exchange rate exists in the system for a certain rate
    type, source currency mnemonic, target currency mnemonic, and is effective
    from 12:00 15 July 1998 until 12:30 15 July 1998. Now suppose we attempt to
    insert an exchange rate for the same rate type, source/target currency
    mnemonics and is effective from 11:45 15 July 1998 until 12:15 15 July
    1998. How does the insertExchangeRate() interface react in this case, or in
    any other case where the exchange rate to be inserted has an effective
    window in time that in whole or in part overlaps existing exchange rate
    data?

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Create mechanism to modify what negative prefix is for formatting string

  • Key: CURR11-69
  • Legacy Issue Number: 2414
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: There is no mechanism to modify what the negative prefix is, in a formatted
    string. You can modify what the placeholder for the negative prefix is, but
    not the actual prefix. This then means that "-" is to be used in every
    locale. I would bet that we should support changing that character ... much
    like we allow changing the radix character or the grouping character.
    Hence, [gs]etNegativePrefixSymbol() above.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarify exceptions for setFormattingString in MoneyFormatter

  • Key: CURR11-66
  • Legacy Issue Number: 2411
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Need to indicate that an exception will be thrown if setFormattingString()
    is called with formattingString being an empty string or one containing
    white space only.

  • Reported: CURR 1.0 — Tue, 2 Feb 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarify contradiction betw setFormatByLocale & setFormattingString

  • Key: CURR11-65
  • Legacy Issue Number: 2410
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It appears that setFormatByLocale() and setFormattingString() override each
    other, but the supporting text for each does not support this conclusion.
    If setFormatByLocale() is executed, and then a call to
    getFormattingString() is executed, a format specification for the given
    locale should be returned correct? If a call to setFormattingString() is
    then executed (which would change the format specification for the given
    state identifier from the locale based specification previously),
    getFormattingString() then returns the format specification just assigned
    correct? The supporting text needs to address this behavior.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Interface changes for MoneyFormatter pattern handling

  • Key: CURR11-68
  • Legacy Issue Number: 2413
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Interface changes for MoneyFormatter pattern handling

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Typo on SetPatternMnemonicSymbol name

  • Key: CURR11-67
  • Legacy Issue Number: 2412
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Fix typo to setPatternMnemonicSymbol()

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add interfaces for internal precision on MoneyCalculator

  • Key: CURR11-71
  • Legacy Issue Number: 2416
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Propose the following interface change(s):
    short getInternalPrecision(in
    CosObjectIdentity::IdentifiableObject stateIdentifier)
    void setInternalPrecision(in
    CosObjectIdentity::IdentifiableObject stateIdentifier,
    short precision) – See example of use of this in the
    MoneyCalculator Interface section.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    Already resolved in a previous issue (2271)

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarify on comparison methods of the MoneyCalculator

  • Key: CURR11-70
  • Legacy Issue Number: 2415
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Clarify on comparison methods of the calculator that no rounding etc. would
    take place before the comparison, it would be the raw numbers in each
    money instance that is compared.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarify MoneyFormatter use of the # symbol

  • Key: CURR11-63
  • Legacy Issue Number: 2408
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Clarify how the ‘#’ is used in the money formatter – i.e. if the digit is
    zero and doesn’t contribute to the value, 0 will not show.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Proposed interface changes to ExchangeRateManager

  • Key: CURR11-62
  • Legacy Issue Number: 2407
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Propose the following interface changes:
    ExchangeRate createExchangeRate(
    in wstring rateTypeId,
    in wstring sourceCurrencyMnemonic,
    in wstring targetCurrencyMnemonic,
    in CBO::Ddecimal conversionFactor,
    in CBO::Dtime beginDateTime,
    in CBO::Dtime endDateTime)

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    Close, no action

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Fix omitted precondition for MoneyCalculator

  • Key: CURR11-72
  • Legacy Issue Number: 2417
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Issue Description: What are the legal short precision values which can be
    presented to setInternalPrecision()? Should it be limited to values >= 0?

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Change the name of addExchangeRate to insertExchangeRate

  • Key: CURR11-59
  • Legacy Issue Number: 2404
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The addExchangeRate() method name could connote mathematical summation.
    Change the method name to insertExchangeRate().

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Exchange rates need to be date based.

  • Key: CURR11-34
  • Legacy Issue Number: 2369
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: In Fbc: Need the ability to have date based exchange rates and for the
    manager to manage date based exchange rates.

    • Since we need to start accounting for dates for exchange of currencies
      and also for doing multi-currency money calculations, it would be nice to
      add settings on the ExchangeRateManager that is state based that allows for
      client configuration.
  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clearer information describing different rounding types is needed

  • Key: CURR11-33
  • Legacy Issue Number: 2368
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: RoundingType.ROUND_DOWN – The textual description needs to be far more
    explicit and/or include examples for both positive and negative numbers.
    Round toward zero? Is the rounding digit truly ignored? e.g. Let the
    internal precision be two.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved in Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Text indicating that vendors shall provide default values

  • Key: CURR11-32
  • Legacy Issue Number: 2367
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: .A Currency implementation should probably provide default values on behalf
    of a given valid stateIdentifier (i.e. MoneyCalculator.roundingType,
    MoneyCalculator.roundingDigit, MoneyCalculator.conversionType,
    MoneyCalculator.internalPrecision, MoneyFormatter.radixSymbol,
    MoneyFormatter.groupingSymbol, MoneyFormatter.negativePrefixSymbol,
    MoneyFormatter.inputMultiplier, MoneyFormatter.outputDivisor, locale,
    etc.). The standard should state that a vendor’s responsibility is to
    provide defaults, but leave the choice of the actual default values to the
    vendor. An interface allowing state to be set back to defaults should be
    considered.

  • Reported: CURR 1.0 — Mon, 1 Feb 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolve dis Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Extend ExceptionType enumerations

  • Key: CURR11-31
  • Legacy Issue Number: 2366
  • Status: closed  
  • Source: Anonymous
  • 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.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved in Currency 2 RTF, closed

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Propose modification to the init method of CurrencyValue

  • Key: CURR11-36
  • Legacy Issue Number: 2381
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Propose the following interface change(s):
    void init(
    in wstring name,
    in wstring fractionName,
    in wstring mnemonic,
    in short numericCode,
    in wstring symbol,
    in wstring fractionSymbol,
    in short ratioOfFractionToWhole,
    in wstring description,
    in CBO::DTime introductionDate,
    in CBO::DTime expirationDate,
    in boolean isISO,
    in wstring ISOVersion,
    in StringCollection locales)
    raises(FbcException); - Note in this signature that
    scaleFactor, isExternalOutputShowingFractions, and
    isInternalOutputShowingFractions have been deleted.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved in Currency 2 RTF, closed

  • Updated: Fri, 6 Mar 2015 20:58 GMT

vendor implementations can implement only parts and interoperate-Statement

  • Key: CURR11-35
  • Legacy Issue Number: 2379
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The specification should state very explicitly how the subsystems/entry
    points (i.e. StateIdManager, CurrencyBook, ExchangeRateManager,
    MoneyFormatter, MoneyCalculator) locate each other if multiple vendor
    implementations (e.g. StateIdManager and MoneyFormatter implementation from
    one vendor and the remaining from another) can work with each other. If the
    intention though is to support homogeneous implementations only (i.e. A
    vendor solution supports all subsystems/entry points and only works with
    its one implementation) this needs to be called out in the specification
    instead.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    No action taken, this has always been viewed as a component.

  • Updated: Fri, 6 Mar 2015 20:58 GMT

More clarification on the semantics of string arguements for CurrencyValue

  • Key: CURR11-39
  • Legacy Issue Number: 2384
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Can the wstring argument(s) to setMnemonic(), setName(), setFractionName(),
    setSymbol(), setFractionSymbol(), or init() be empty strings or strings
    containing only white space? Acceptable arguments need to be discussed.

  • Reported: CURR 1.0 — Tue, 2 Feb 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF, closed

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Missing details on preconditions on the Currency interface as a whole

  • Key: CURR11-38
  • Legacy Issue Number: 2383
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Missing details on preconditions on the Currency
    interface as a whole

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed issue, resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Typos in CurrencyValue section

  • Key: CURR11-41
  • Legacy Issue Number: 2386
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Typos in the section that describes setRatioOfFractionToWhole(). The second
    sentence should be “The ratio for United States Dollars is one hundred
    pennies to one dollar, which is 100. In cases where there is no minor part
    of a currency (e.g. Yen), this method should return a value of 1.”

  • Reported: CURR 1.0 — Tue, 2 Feb 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved by Currency 2 RTF, close

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Legal value ranges for numerics in CurrencyValue init should be discussed

  • Key: CURR11-40
  • Legacy Issue Number: 2385
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Can the short numericCode presented to init() and setNumericCode() be <= 0?
    What are its legal values?
    Can the short ratioOfFractionToWhole provided to init() and
    setRatioOfFractionToWhole() be <= 1? What are acceptable values?
    Can the point in time represented by introductionDate be >= expirationDate
    in init() and setExpirationDate()/setIntroductionDate()?

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    close issue, resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

missing description on the init method for CurrencyValue

  • Key: CURR11-37
  • Legacy Issue Number: 2382
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: The init() method appears in the consolidated IDL Specifications portion of
    the standard, but does not appear and is not documented or discussed in
    section 2.3.6.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    closed issue, resolved by Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

StateID Exception

  • Key: CURR11-30
  • Legacy Issue Number: 2363
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Need exceptions for stateId indicating that one was never created from the
    StateIdManager for all methods that take stateId.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved is Currency 2 RTF, closed

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Change double to short for internal precision

  • Key: CURR11-29
  • Legacy Issue Number: 2271
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Change double to short for internal precision

  • Reported: CURR 1.0 — Fri, 18 Dec 1998 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved in Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add idl and text to describe the getAllExchangeRates method

  • Key: CURR11-28
  • Legacy Issue Number: 2270
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Add idl and text to describe the getAllExchangeRates method

  • Reported: CURR 1.0 — Fri, 18 Dec 1998 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved in Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add text for formatter that the format string will be used for parsing

  • Key: CURR11-27
  • Legacy Issue Number: 2269
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Add text for formatter that the format string will be used for parsing.
    Clarify the formatting string and how it is used.
    This way the parser routine will use: M##,###.00 to help it parse: RUR10,00
    This also means the radix character was set to: "," and the grouping symbol was set to: "."
    Show an example to distinguish between what the pattern gives you and what the actually settings of the characters give you.

  • Reported: CURR 1.0 — Thu, 17 Dec 1998 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved in Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Change text description of behavior of ROUND_FLOOR and ROUND_CEILING

  • Key: CURR11-26
  • Legacy Issue Number: 2268
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Change text description of behavior of ROUND_FLOOR and ROUND_CEILING. The descriptions are mixed between the two.

  • Reported: CURR 1.0 — Thu, 17 Dec 1998 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    Change text in spec describing the correct behaviour for the rounding rules

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarify on comparison methods of the calculato

  • Key: CURR11-25
  • Legacy Issue Number: 2267
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Clarify on comparison methods of the calculator that no rounding etc. would take place before the
    comparison, it would be the raw numbers in each money instance that is compared.

  • Reported: CURR 1.0 — Thu, 17 Dec 1998 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    Already fixed in issue # 2415

  • Updated: Fri, 6 Mar 2015 20:58 GMT

clarification on how the "#" is used in the money formatter

  • Key: CURR11-24
  • Legacy Issue Number: 2265
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Need more clarification on how the "#" is used in the money formatter -
    i.e. if the digit is zero and doesn"t contribute to the value, 0 will not show.

  • Reported: CURR 1.0 — Thu, 17 Dec 1998 05:00 GMT
  • Disposition: Resolved — CURR 1.1
  • Disposition Summary:

    resolved and closed in Currency 2 RTF

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Place maximums on wstrings for interoperability

  • Key: CURR11-21
  • Legacy Issue Number: 2781
  • Status: open  
  • Source: Anonymous
  • Summary:

    Should the interfaces that accept a wstring also somehow state the maximum length of that data string? This is necessary for the implementation to know the maximum number of wide characters that may need to be stored in a persistence repository. e.g. Currency.mnemonic is three? This also includes the following : Currency.name, Currency.fractionName, Currency.symbol, Currency.fractionSymbol, Currency.description, Currency.ISOVersion, a locale wstring, ExchangeRate.rateType, CurrencyBook.publishedVersion, MoneyFormatter.formattingString, MoneyFormatter.groupingSymbol, MoneyFormatter.negativePrefixSymbol, MoneyFormatter.radixSymbol.

  • Reported: CURR 1.0 — Wed, 30 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add interfaces to DTime properly handle the DAmountOfTime difference inter

  • Key: CURR11-15
  • Legacy Issue Number: 2427
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: DAmountOfTime difference(in DTime anotherTime) does not support an
    implementation properly as the difference between two points in time is a
    DamountOfTime instance and DamountOfTime represents an “absolute (positive)
    amount of time”. Thus, either DamountOfTime must be able to represent an
    amount of time that is less than zero, or the following interfaces must be
    available.
    · Propose the following additional interfaces:
    boolean equal(in CBO::Dtime otherObject);
    void setEqual(in CBO::Dtime otherObject);
    boolean less(in CBO::Dtime otherObject);
    boolean lessEqual(in CBO::Dtime otherObject);
    boolean greater(in CBO::Dtime otherObject);
    boolean greaterEqual(in CBO::Dtime otherObject);

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Improve text in specification of of DAmountOfTime

  • Key: CURR11-17
  • Legacy Issue Number: 2430
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The toWeeks(), toDays(), and toHours()operations return the amount to the
    nearest whole unit. The toMinutes() and toSeconds() operations are not
    specified in the same way, and the commentary for these two operations uses
    such poor English that the intention is not clear.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Support millisecond precision in DAmountOfTime

  • Key: CURR11-16
  • Legacy Issue Number: 2429
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Issue Description: Cannot represent milliseconds or any sub-second
    precision

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Changing RoundType.DONT_ROUND

  • Key: CURR11-20
  • Legacy Issue Number: 2780
  • Status: open  
  • Source: Anonymous
  • Summary:

    DO_NOT_ROUND would be more explicit and prohibit confusion as the contraction might cause some confusion.

  • Reported: CURR 1.0 — Wed, 30 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add ability to clone Money

  • Key: CURR11-19
  • Legacy Issue Number: 2778
  • Status: open  
  • Source: Anonymous
  • Summary:

    Need the ability to clone Money from existing Money

  • Reported: CURR 1.0 — Wed, 30 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Remove Depedence in FBCCurrency of CBO::DDecimal

  • Key: CURR11-23
  • Legacy Issue Number: 2783
  • Status: open  
  • Source: Anonymous
  • Summary:

    Replace DDecimal with CORBA fixed type.

  • Reported: CURR 1.0 — Wed, 30 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Remove Dependence in FBCCurrency of CBO::DTime

  • Key: CURR11-22
  • Legacy Issue Number: 2782
  • Status: open  
  • Source: Anonymous
  • Summary:

    Replace DTime in FBCCurrency with struct

  • Reported: CURR 1.0 — Wed, 30 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Remove dependence on a specific version of the ISO 4217 standard

  • Key: CURR11-18
  • Legacy Issue Number: 2776
  • Status: open  
  • Source: Anonymous
  • Summary:

    All throughout the spec it references ISO 4217:1995, it would be better to reference the latest ISO 4217 standard (i.e. no hard-coded date/year).

  • Reported: CURR 1.0 — Wed, 30 Jun 1999 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

: Change name of interface to CBO::Decima

  • Key: CURR11-8
  • Legacy Issue Number: 2420
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Issue Description: Change name of interface to CBO::Decimal.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Corrections to the equals/setEquals interfaces of DTime

  • Key: CURR11-7
  • Legacy Issue Number: 2419
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The equals/setEquals() interfaces accept a base class CORBA Object as the
    parameter type. The instance passed must be narrow’ed to a DDecimal, DTime,
    etc. for the interface to carry on with its task. This is not possible as
    the Ddecimal, Dtime, etc. are not IDL Interfaces, they are IDL Value types.
    Since an IDL Value type does not derive from Object, the narrow’ing is not
    possible. This also affects other portions of the CBO … DCurrency, DMoney,
    etc. Also, equals(in Object anObject) causes a problem in a Java
    implementation as every Java class inherits from java.lang.Object. The
    boolean equals(Object obj) method supported by java.lang.Object cannot be
    overriden AND additional throw an FbcException. Thus, equals(), setEquals()
    should be changed wherever defined to be equal(), setEqual().

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Improve DTime exception handling

  • Key: CURR11-6
  • Legacy Issue Number: 2418
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The CBOException type currently prohibits the called software from
    informing the calling software as to the source of the problem that raises
    a CBOException. e.g. If CBO::DTime::setSeconds(63) is called, a
    CBOException will be raised, but the caller cannot query the CBOException
    caught for its exception type or description as CBOException does not
    currently support these constructs. In the case where many arguments are
    presented to a method, the caller will not know which specific argument is
    causing the problem.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add interface to DTime

  • Key: CURR11-14
  • Legacy Issue Number: 2426
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The Currency submission indicates that a specific Currency instance that
    does not have an expiration date will be noted with an expiration date of
    99/99/9999. This attribute is handled via a CBO::Dtime instance, but a
    CBO::Dtime instance cannot be created or mutated to represent 99/99/9999.
    e.g. The CBO::Dtime::setMonth(mon) expects 1 <= 12, etc. Would probably be
    easiest to have two operations on CBO::Dtime to handle this. These could
    be:
    void setUnspecified() – might be handled in an implementation as
    99/99/9999.
    boolean isUnspecified() – insulates the consumer from knowing how
    the notion of “unspecified” is implemented.

  • Reported: CURR 1.0 — Tue, 2 Feb 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarification required on setYear of the DTime interface

  • Key: CURR11-13
  • Legacy Issue Number: 2425
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The setYear(in long year) interface is described such that year is
    expressed in four digit form. Does this then mean that year must be >= 1000
    or that year indicates an absolute year after christ? e.g. 99 means 99 and
    not 1999?

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

support to set precision to something other than milliseconds

  • Key: CURR11-12
  • Legacy Issue Number: 2424
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Cannot set precision to something other than milliseconds, as DAmountOfTime
    cannot represent sub-second resolution. Cannot set the millisecond portion
    of the point in time as the Factory does not take the number of
    milliseconds as an argument, nor does the init() method.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

describe how the individual components should be accessed

  • Key: CURR11-5
  • Legacy Issue Number: 2380
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Should the subsystem/singleton components (i.e. StateIdManager,
    CurrencyBook, ExchangeRateManager, MoneyFormatter, MoneyCalculator) all be
    published separately to the CORBAservices Naming Service?

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Description of Exception handling semantics

  • Key: CURR11-4
  • Legacy Issue Number: 2365
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Text needs to be added to describe what causes an exception to be raised
    for a given interface, when the semantics/preconditions for the interface
    have been violated (vs. exceptions specific to a vendor
    ’s implementation).
    e.g. Money.[gs]etValue(), MoneyFormatter.[gs]etFormattingString(), etc. It
    appears that most every interface raises (FbcException), but quite often
    the text which describes which exceptions can be raised, in terms of
    ExceptionType and under what conditions the exception is raised/thrown, has
    not been detailed. A detailed pass through the entire FbcCurrency spec
    should be conducted with attention paid to each interface and its exception
    generating details.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add text for DTime and DDecimal from CBO submission into Currency spec.

  • Key: CURR11-3
  • Legacy Issue Number: 2273
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Now that the CBO submission no longer exists, we need to add the text for DTime and DDecimal
    from the CBO submission into the Currency Spec.

  • Reported: CURR 1.0 — Fri, 18 Dec 1998 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

: Change name of interface to CBO::Time

  • Key: CURR11-11
  • Legacy Issue Number: 2423
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Issue Description: Change name of interface to CBO::Time.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add interfaces to DDecimal

  • Key: CURR11-10
  • Legacy Issue Number: 2422
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Make the following interface changes:
    boolean equal(in DDecimal otherObject);
    void setEqual(in DDecimal otherObject);

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clarify the equality method of DDecimal

  • Key: CURR11-9
  • Legacy Issue Number: 2421
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Issue Description: Clarify comparisons of two CBO::Ddecimal values on
    equality (i.e. 2.0 equal to 2.000)
    – regardless of scale factor.

  • Reported: CURR 1.0 — Mon, 11 Jan 1999 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

The idl for CBO::DTime needs the method: long getYear()

  • Key: CURR11-2
  • Legacy Issue Number: 2272
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The idl for CBO::DTime needs the method: long getYear()

  • Reported: CURR 1.0 — Fri, 18 Dec 1998 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clairfy comparisons of two CBO::Ddecimal values on equality

  • Key: CURR11-1
  • Legacy Issue Number: 2266
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Clairfy comparisons of two CBO::Ddecimal values on equality (i.e. 2.0 equal to 2.000)
    regardless of scale factor

  • Reported: CURR 1.0 — Thu, 17 Dec 1998 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT