JDK-4286518 : Clarification on serialization form changes in SimpleTimeZone
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 1.3.0
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1999-11-01
  • Updated: 1999-11-12
  • Resolved: 1999-11-12
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
1.3.0 kestrelFixed
Related Reports
Relates :  
JDK-4191164 - TimeZone Europe/London (and EU countries) is incorrect
Description
The SimpleTimeZone changes for the 4191164 fix involved serialization form changes. It is desirable to fix the bug without the serialization form changes.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: kestrel FIXED IN: kestrel INTEGRATED IN: kestrel
14-06-2004
EVALUATION Looking into a way to fix 4191164 without the serialization form changes. Probably the fix requires other bug fixes about boundary cases on DST transition. masayoshi.okutsu@Eng 1999-11-01 Two field, int startTimeMode and int endTimeMode has been added by changes of 4191164 and one value defined for serialVersionOnStream. Since this change has not reviewed or approved by CCC, the attempt has been made to remove the change. However, without UTC/Standard time mode, some time zones' daylight saving transition time would be nagative value. And since SimpleTimeZone calculation assumes daylight saving transition time is positive value, nagative daylight saving transition time breaks these codes. The further attempt made to change calcuration. However this approach breaks serialization compatibility to previous version of JDK. Then, the best approach to this problem is to get CCC approval for the change of 4191164 and keep current code unchanged. koushi.takahashi@japan 1999-11-05 The change of 4191164 has been approved by CCC, as kestrel beta implementation. koushi.takahashi@japan 1999-11-12
05-11-1999