This SPI-interface describes when UTC-leapseconds were introduced.
Will be evaluated during loading of the class
If any implementation defines no leapseconds then Time4J assumes
that leapseconds will generally not be active, effectively resulting
in POSIX-time instead of UTC.
Note: All implementations must have a public no-arg constructor.
- Meno Hochschild
Method SummaryModifier and TypeMethodDescription
(int year, int month, int dayOfMonth)Creates the date of a leap second event.
()Determines the expiration date of underlying data.
()Yields all UTC-leapseconds with date and sign.
()Queries if negative leapseconds are supported.
Yields all UTC-leapseconds with date and sign.
The switch-over day in the UTC-timezone is considered as map key. The associated value is denotes the sign of the leapsecond. Is the value
+1then it is a positive leapsecond. Is the value
-1then it is a negative leapsecond. Other values are not supported.
- map from leap second event day to sign of leap second
Queries if negative leapseconds are supported.
Until now there has never been any negative leapseconds. As long as this is the case a
Provideris allowed to return
falsein order to improve the performance.
trueif supported else
getDateOfEventGregorianDate getDateOfEvent(int year, int month, int dayOfMonth)
Creates the date of a leap second event.
year- proleptic gregorian year >= 1972
month- gregorian month
dayOfMonth- day of leap second switch
- immutable date of leap second event
Determines the expiration date of underlying data.
- immutable date of expiration