JDK-4690258 : Doc: Calendar.HOUR numbering is not documented
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 1.4.0,1.4.1
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,linux
  • CPU: generic,x86
  • Submitted: 2002-05-23
  • Updated: 2003-12-16
  • Resolved: 2003-12-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b32Fixed
Related Reports
Duplicate :  
JDK-4878119 - Calendar.get(Calendar.HOUR) returns 0 for the midnight hour, not 12
Relates :  
JDK-4074758 - Calendar.HOUR returns 0 for 12 am/pm instead of 12
Relates :  
JDK-4689930 - Calendar: AM_PM not recognized when setting HOUR
Description
The Calendar.HOUR numbering is not documented. The HOUR numbering is not 12, 1, 2, 3, ..., 11, but 0, 1, 2, ..., 11. In Calendar API, some numbering is different from the real life numbering. For example, months are numbered as 0, 1, 2, ..., 11 (in Calendar API and C library), not 1, 2, 3, ..., 12.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta FIXED IN: tiger-beta INTEGRATED IN: tiger-b32 tiger-beta
14-06-2004
EVALUATION The HOUR numbering must be documented. ###@###.### 2003-12-03
03-12-2003