Class ZoneHistory
Off unless a project asks for it. The platform's own database answers every question about an
offset, and IntlZoneRules derives the rest from that, but it cannot list the changes a zone
has had or the rules by which they recur, so those refuse. Calling register() installs this
as their answer, and the generated entry point does that when the build sets
classlib { zoneHistory = true }. A program that never names this class never links it, and
the 108 KB database is only copied into the module when it is linked: see ZoneResources.
The file is read here rather than through ThreeTen's own reader, because that reader builds the
rules class this package replaces. What is built instead is plain transitions and rules through
their public factories, which is all ZoneRules.getTransitions() and
getTransitionRules() return.
Only these two answers come from the bundle. Offsets, daylight saving and the search for the next change stay with the platform, so a platform whose database is newer than the bundle can disagree with the history it is shown.
- Since:
- 1.0.3
-
Method Summary
Modifier and TypeMethodDescriptionbooleanstatic voidregister()Makes the recorded history of a zone available, which is what the generated entry point calls.transitions(String zoneId)
-
Method Details
-
register
public static void register()Makes the recorded history of a zone available, which is what the generated entry point calls. -
transitions
-
rules
-
covers
-
next
-
previous
-