I noticed the following -
- Where tzdata has DST rules like 1996 to max (EU), the DST continues indefinitely (or at least to 100 years after compiling)
- A comment in the class "org.joda.time.tz.DateTimeZoneBuilder", method "toDateTimeZone(String id, boolean outputID)" reads "// Tail zone picks up remaining transitions in the form of an endless DST cycle." The tailzone for the kind of zone without max given results in null (due to max not being specified in the tzdata)
- A tailzone is built in the method "public DSTZone buildTailZone(String id)" in the class "org.joda.time.tz.DateTimeZoneBuilder", but it will only do so if the rules start year and end year are equal to max int value, else it returns null
- JDKs (JRockit, HotSpot and IBM J9) seem to apply the last rule in 2037 further onwards for subsequent years
To summarize - I am not sure if (not) applying DST transitions past the last year specified in tzdata, where max is not given, is a bug or a design decision?
Try FREE IM ToolPack at www.imtoolpack.com
Works in all emails, instant messengers, blogs, forums and social networks.
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Joda-interest mailing list Joda-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/joda-interest