Currency Service Avatar
  1. OMG Specification

Currency Service — Open Issues

  • Acronym: CURR
  • Issues Count: 23
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Summary

Key Issue Reported Fixed Disposition Status
CURR11-22 Remove Dependence in FBCCurrency of CBO::DTime CURR 1.0 open
CURR11-23 Remove Depedence in FBCCurrency of CBO::DDecimal CURR 1.0 open
CURR11-21 Place maximums on wstrings for interoperability CURR 1.0 open
CURR11-18 Remove dependence on a specific version of the ISO 4217 standard 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-19 Add ability to clone Money CURR 1.0 open
CURR11-15 Add interfaces to DTime properly handle the DAmountOfTime difference inter CURR 1.0 open
CURR11-20 Changing RoundType.DONT_ROUND 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-14 Add interface to DTime CURR 1.0 open
CURR11-11 : Change name of interface to CBO::Time CURR 1.0 open
CURR11-7 Corrections to the equals/setEquals interfaces of DTime CURR 1.0 open
CURR11-9 Clarify the equality method of DDecimal CURR 1.0 open
CURR11-8 : Change name of interface to CBO::Decima CURR 1.0 open
CURR11-6 Improve DTime exception handling CURR 1.0 open
CURR11-10 Add interfaces to DDecimal CURR 1.0 open
CURR11-3 Add text for DTime and DDecimal from CBO submission into Currency spec. CURR 1.0 open
CURR11-4 Description of Exception handling semantics CURR 1.0 open
CURR11-5 describe how the individual components should be accessed 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

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 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

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

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

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

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

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

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

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

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

: 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

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

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

: 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

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 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

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

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

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

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