FULL PRODUCT VERSION :
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
windows 2003 sp2

A DESCRIPTION OF THE PROBLEM :
according to the CLDR, en_AU & en_NZ use "h:mm:ss a" time pattern. common practice also indicates the pattern should be "h:mm:ss a".  however core java seems to use "H:mm:ss" which means it can't correctly format or parse commonly used time patterns from those locales.



REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
use icu4j but applications like  customer 's coldfusion are stuck w/core java locale data.
Posted Date : 2007-05-17 17:13:56.0

N/A

condisering the request approval, will first fix and integrate it in java 7 and then move to jdk 6 update. Plan to integrate in 6u4 first.
Posted Date : 2007-05-18 06:28:46.0

change responsible engineer to Jiri. sorry that I did not realize Jiri is in charge of locale bug including non-eu locales.
Posted Date : 2007-05-18 07:49:30.0

Fix:
j2se:src/share/classes/sun/text/resources/FormatData_en_AU.java
j2se:src/share/classes/sun/text/resources/FormatData_en_NZ.java
------- FormatData_en_AU.java -------
54c54
<                     "H:mm:ss", // long time pattern
---
>                     "h:mm:ss a", // long time pattern

------- FormatData_en_NZ.java -------
54c54
<                     "H:mm:ss", // long time pattern
---
>                     "h:mm:ss a", // long time pattern

test:
j2se:test/closed/sun/text/resources/LocaleDataTest.java
j2se:test/closed/sun/text/resources/LocaleData
modify:
> # bug #4094371, 4098518, 4290801, 6558863
292c292
< FormatData/en_AU/DateTimePatterns/1=H:mm:ss
---
> FormatData/en_AU/DateTimePatterns/1=h:mm:ss a
315c315
< FormatData/en_NZ/DateTimePatterns/1=H:mm:ss
---
> FormatData/en_NZ/DateTimePatterns/1=h:mm:ss a
Posted Date : 2007-05-21 12:09:57.0