Turkey is going to introduce a new currency, the New 
Turkish Lira, on January 1, 2005. The ISO 4217 currency code is TRY, 
the currency  customer  YTL, and it's subdivided into 100 New Kuru\u015F. 
For more information, see the FAQ of the Central Bank of the Republic 
of Turkey at http://www.tcmb.gov.tr/yeni/iletisimgm/NTL_faq.htm.

The currency data and the Turkish locale data need to be updated for 
this change.

Note that on January 1, 2006, when the (old) Turkish Lira becomes 
invalid, the "New" and "Y" are dropped from the name and  customer  of the 
new currency.
======================================================================
  xxxxx@xxxxx   10/12/04 18:31 GMT

???
======================================================================

Need updated currency info in 1.4.2_xx and 5.0_xx before 
1/1/2005.
======================================================================
verified in 5.0u1 b05 on JDS3-linux b21.

  xxxxx@xxxxx  
  xxxxx@xxxxx   11/2/04 18:10 GMT

Nice to read this bug has been fixed. It's just that it's not enough to fix it in mustang. As the author of the bug mentioned this fix should be applied to more ore less all jdks that are still in use (I'm working for a bank - we have to work with the new turkish Lira since 1/1/2005).

Alltogether the problem is that at any point in time we may have to face a new currency that's coming up and java.util.Currency has to be implemented in a way that customers can add new currency themselves.

Please check bug 4990462 for a more general description of the problem...

Unfortunately, the bug crashed an application in production environment. Now I need to find a suitable jdk to replace the running one, and hope to have no issues.
This kind of exception was unchecked in the application, because we have a strict control on ISO currency codes, and we assumed that the table was configurable by the user on the Java runtime Environment.