net.time4j.scale

Interface LeapSecondProvider

public interface LeapSecondProvider

This SPI-interface describes when UTC-leapseconds were introduced.

Will be evaluated during loading of the class LeapSeconds. If any implementation defines no leapseconds then Time4J assumes that leapseconds will generally not be active, effectively resulting in POSIX-time instead of UTC.

Since:

2.0

Author:

Meno Hochschild

Method Summary

Methods

Modifier and Type	Method and Description
Map<GregorianDate,Integer>	getLeapSecondTable() Yields all UTC-leapseconds with date and sign.
boolean	supportsNegativeLS() Queries if negative leapseconds are supported.

Method Detail

getLeapSecondTable

Map<GregorianDate,Integer> getLeapSecondTable()

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 +1 then it is a positive leapsecond. Is the value -1 then it is a negative leapsecond. Other values are not supported.

Returns:

map from leap second event day to sign of leap second

supportsNegativeLS

boolean supportsNegativeLS()

Queries if negative leapseconds are supported.

Until now there has never been any negative leapseconds. As long as this is the case a Provider is allowed to return false in order to improve the performance.

Returns:

true if supported else false