-
Bug
-
Resolution: Fixed
-
P4
-
25
-
b20
-
generic
-
generic
Currency currently checks that a future currency that is not yet defined should not be included in the output returned by Currency.getAvailableCurrencies(). What should also be included is a check that ensures that Currency.getCurrentInstance(String) throws an IllegalArgumentException for such cases.
For example,
For an entry such as : "SX=ANG;2025-04-01-04-00-00;XCG"
If the current date was before the cut over, as XCG is not an already existing ISO 4217 currency code, it should not exist in the output of available currencies and should not be instantiable by getInstance(String).
Conversely, if the entry had been : "SX=ANG;2025-04-01-04-00-00;EUR", we would expect it to be both in the output of available currencies and instantiable since EUR is an already existing ISO 4217 currency code.
For example,
For an entry such as : "SX=ANG;2025-04-01-04-00-00;XCG"
If the current date was before the cut over, as XCG is not an already existing ISO 4217 currency code, it should not exist in the output of available currencies and should not be instantiable by getInstance(String).
Conversely, if the entry had been : "SX=ANG;2025-04-01-04-00-00;EUR", we would expect it to be both in the output of available currencies and instantiable since EUR is an already existing ISO 4217 currency code.
- relates to
-
JDK-8321480 ISO 4217 Amendment 176 Update
-
- Closed
-
- links to
-
Commit(master) openjdk/jdk/ac41bc31
-
Review(master) openjdk/jdk/24782