OpenJDK 1.22 · java.time.chrono.IsoChronology · APIdia, the JavaDoc alternative

Modifier and Type	Field and Description
private static final long	DAYS_0000_TO_1970
public static final IsoChronology	INSTANCE Singleton instance of the ISO chronology.
private static final long	serialVersionUID Serialization version.

Access	Constructor and Description
private	IsoChronology() Restricted constructor.

Method Summary

Modifier and Type	Method and Description
public LocalDate	Returns: the ISO local date, not null date(Era the ISO era, not null era, int the ISO year-of-era yearOfEra, int the ISO month-of-year month, int the ISO day-of-month dayOfMonth) Overrides default java.time.chrono.Chronology.date. Obtains an ISO local date from the era, year-of-era, month-of-year and day-of-month fields.
public LocalDate	Returns: the ISO local date, not null date(int the ISO proleptic-year prolepticYear, int the ISO month-of-year month, int the ISO day-of-month dayOfMonth) Implements java.time.chrono.Chronology.date. Obtains an ISO local date from the proleptic-year, month-of-year and day-of-month fields.
public LocalDate	Returns: the ISO local date, not null date(TemporalAccessor the date-time object to convert, not null temporal) Implements java.time.chrono.Chronology.date. Obtains an ISO local date from another date-time object.
public LocalDate	Returns: the ISO local date, not null dateEpochDay(long the epoch day epochDay) Implements java.time.chrono.Chronology.dateEpochDay. Obtains an ISO local date from the epoch-day.
public LocalDate	Returns: the current ISO local date using the system clock and default time-zone, not null dateNow() Overrides default java.time.chrono.Chronology.dateNow. Obtains the current ISO local date from the system clock in the default time-zone.
public LocalDate	Returns: the current ISO local date using the system clock, not null dateNow(ZoneId the zone ID to use, not null zone) Overrides default java.time.chrono.Chronology.dateNow. Obtains the current ISO local date from the system clock in the specified time-zone.
public LocalDate	Returns: the current ISO local date, not null dateNow(Clock the clock to use, not null clock) Overrides default java.time.chrono.Chronology.dateNow. Obtains the current ISO local date from the specified clock.
public LocalDate	Returns: the ISO local date, not null dateYearDay(Era the ISO era, not null era, int the ISO year-of-era yearOfEra, int the ISO day-of-year dayOfYear) Overrides default java.time.chrono.Chronology.dateYearDay. Obtains an ISO local date from the era, year-of-era and day-of-year fields.
public LocalDate	Returns: the ISO local date, not null dateYearDay(int the ISO proleptic-year prolepticYear, int the ISO day-of-year dayOfYear) Implements java.time.chrono.Chronology.dateYearDay. Obtains an ISO local date from the proleptic-year and day-of-year fields.
public long	Returns: the number of seconds relative to 1970-01-01T00:00:00Z, may be negative epochSecond(int the year, from MIN_YEAR to MAX_YEAR prolepticYear, int the month-of-year, from 1 to 12 month, int the day-of-month, from 1 to 31 dayOfMonth, int the hour-of-day, from 0 to 23 hour, int the minute-of-hour, from 0 to 59 minute, int the second-of-minute, from 0 to 59 second, ZoneOffset the zone offset, not null zoneOffset) Overrides default java.time.chrono.Chronology.epochSecond. Gets the number of seconds from the epoch of 1970-01-01T00:00:00Z.
public IsoEra	eraOf(int the era value eraValue) Implements java.time.chrono.Chronology.eraOf. Creates the chronology era object from the numeric value.
public List<Era>	eras() Implements java.time.chrono.Chronology.eras. Gets the list of eras for the chronology.
public String	Returns: the calendar system type - 'iso8601' getCalendarType() Implements java.time.chrono.Chronology.getCalendarType. Gets the calendar type of the underlying calendar system - 'iso8601'.
public String	Returns: the chronology ID - 'ISO' getId() Implements java.time.chrono.Chronology.getId. Gets the ID of the chronology - 'ISO'.
public boolean	Returns: `true` isIsoBased() Overrides default java.time.chrono.Chronology.isIsoBased. `IsoChronology` is an ISO based chronology, which supports fields in `IsoFields`, such as `DAY_OF_QUARTER` and `QUARTER_OF_YEAR`.
public boolean	Returns: true if the year is leap, false otherwise isLeapYear(long the ISO proleptic year to check prolepticYear) Implements java.time.chrono.Chronology.isLeapYear. Checks if the year is a leap year, according to the ISO proleptic calendar system rules.
public LocalDateTime	Returns: the ISO local date-time, not null localDateTime(TemporalAccessor the date-time object to convert, not null temporal) Overrides default java.time.chrono.Chronology.localDateTime. Obtains an ISO local date-time from another date-time object.
private int	Returns: the number of days for the given month in the given year numberOfDaysOfMonth(int the year to represent, from MIN_YEAR to MAX_YEAR year, int the month-of-year to represent, from 1 to 12 month) Gets the number of days for the given month in the given year.
public Period	Returns: the ISO period, not null period(int the number of years, may be negative years, int the number of years, may be negative months, int the number of years, may be negative days) Overrides default java.time.chrono.Chronology.period. Obtains a period for this chronology based on years, months and days.
public int	prolepticYear(Era the era of the correct type for the chronology, not null era, int the chronology year-of-era yearOfEra) Implements java.time.chrono.Chronology.prolepticYear. Calculates the proleptic-year given the era and year-of-era.
public ValueRange	range(ChronoField the field to get the range for, not null field) Implements java.time.chrono.Chronology.range. Gets the range of valid values for the specified field.
private void	readObject(ObjectInputStream the stream to read s) Hides java.time.chrono.AbstractChronology.readObject. Defend against malicious streams.
public LocalDate	Returns: the resolved date, null if insufficient information to create a date resolveDate(Map<TemporalField, Long> the map of fields to values, which can be updated, not null fieldValues, ResolverStyle the requested type of resolve, not null resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveDate. Implements java.time.chrono.Chronology.resolveDate. Resolves parsed `ChronoField` values into a date during parsing.
pack-priv void	resolveProlepticMonth(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveProlepticMonth.
pack-priv LocalDate	resolveYearOfEra(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveYearOfEra.
pack-priv LocalDate	resolveYMD(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveYMD.
pack-priv Object	Returns: the instance of `Ser`, not null writeReplace() Overrides java.time.chrono.AbstractChronology.writeReplace. Writes the Chronology using a dedicated serialized form.
public ZonedDateTime	Returns: the ISO zoned date-time, not null zonedDateTime(TemporalAccessor the date-time object to convert, not null temporal) Overrides default java.time.chrono.Chronology.zonedDateTime. Obtains an ISO zoned date-time from another date-time object.
public ZonedDateTime	Returns: the zoned date-time, not null zonedDateTime(Instant the instant to create the date-time from, not null instant, ZoneId the time-zone, not null zone) Overrides default java.time.chrono.Chronology.zonedDateTime. Obtains an ISO zoned date-time in this chronology from an `Instant`.

Inherited from java.time.chrono.AbstractChronology:: addFieldValue compareTo equals getAvailableChronologies hashCode of ofLocale readExternal registerChrono registerChrono resolveAligned resolveYAA resolveYAD resolveYD resolveYMAA resolveYMAD toString writeExternal

DAYS_0000_TO_1970	back to summary
private static final long DAYS_0000_TO_1970

INSTANCE	back to summary
public static final IsoChronology INSTANCE Singleton instance of the ISO chronology.

serialVersionUID	back to summary
private static final long serialVersionUID Serialization version. Annotations @Serial

IsoChronology	back to summary
private IsoChronology() Restricted constructor.

Method Detail

date back to summary

date	back to summary
public LocalDate date(Era era, int yearOfEra, int month, int dayOfMonth) Overrides default java.time.chrono.Chronology.date. Obtains an ISO local date from the era, year-of-era, month-of-year and day-of-month fields. Parameters era:Era the ISO era, not null yearOfEra:int the ISO year-of-era month:int the ISO month-of-year dayOfMonth:int the ISO day-of-month Returns:LocalDate the ISO local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date ClassCastException: if the type of `era` is not `IsoEra`

public LocalDate date(Era era, int yearOfEra, int month, int dayOfMonth)

Overrides default java.time.chrono.Chronology.date.

Obtains an ISO local date from the era, year-of-era, month-of-year and day-of-month fields.

Parameters

era:Era: the ISO era, not null
yearOfEra:int: the ISO year-of-era
month:int: the ISO month-of-year
dayOfMonth:int: the ISO day-of-month

Returns:LocalDate

the ISO local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date
ClassCastException:: if the type of era is not IsoEra

date back to summary

date	back to summary
public LocalDate date(int prolepticYear, int month, int dayOfMonth) Implements java.time.chrono.Chronology.date. Obtains an ISO local date from the proleptic-year, month-of-year and day-of-month fields. This is equivalent to `LocalDate#of(int, int, int)`. Parameters prolepticYear:int the ISO proleptic-year month:int the ISO month-of-year dayOfMonth:int the ISO day-of-month Returns:LocalDate the ISO local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public LocalDate date(int prolepticYear, int month, int dayOfMonth)

Implements java.time.chrono.Chronology.date.

Obtains an ISO local date from the proleptic-year, month-of-year and day-of-month fields.

This is equivalent to LocalDate#of(int, int, int).

Parameters

prolepticYear:int: the ISO proleptic-year
month:int: the ISO month-of-year
dayOfMonth:int: the ISO day-of-month

Returns:LocalDate

the ISO local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

date back to summary

date	back to summary
public LocalDate date(TemporalAccessor temporal) Implements java.time.chrono.Chronology.date. Obtains an ISO local date from another date-time object. This is equivalent to `LocalDate#from(TemporalAccessor)`. Parameters temporal:TemporalAccessor the date-time object to convert, not null Returns:LocalDate the ISO local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public LocalDate date(TemporalAccessor temporal)

Implements java.time.chrono.Chronology.date.

Obtains an ISO local date from another date-time object.

This is equivalent to LocalDate#from(TemporalAccessor).

Parameters

temporal:TemporalAccessor: the date-time object to convert, not null

Returns:LocalDate

the ISO local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateEpochDay back to summary

dateEpochDay	back to summary
public LocalDate dateEpochDay(long epochDay) Implements java.time.chrono.Chronology.dateEpochDay. Obtains an ISO local date from the epoch-day. This is equivalent to `LocalDate#ofEpochDay(long)`. Parameters epochDay:long the epoch day Returns:LocalDate the ISO local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public LocalDate dateEpochDay(long epochDay)

Implements java.time.chrono.Chronology.dateEpochDay.

Obtains an ISO local date from the epoch-day.

This is equivalent to LocalDate#ofEpochDay(long).

Parameters

epochDay:long: the epoch day

Returns:LocalDate

the ISO local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateNow back to summary

dateNow	back to summary
public LocalDate dateNow() Overrides default java.time.chrono.Chronology.dateNow. Obtains the current ISO local date from the system clock in the default time-zone. This will query the `system clock` in the default time-zone to obtain the current date. Using this method will prevent the ability to use an alternate clock for testing because the clock is hard-coded. Returns:LocalDate the current ISO local date using the system clock and default time-zone, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public LocalDate dateNow()

Overrides default java.time.chrono.Chronology.dateNow.

Obtains the current ISO local date from the system clock in the default time-zone.

This will query the system clock in the default time-zone to obtain the current date.

Using this method will prevent the ability to use an alternate clock for testing because the clock is hard-coded.

Returns:LocalDate

the current ISO local date using the system clock and default time-zone, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateNow back to summary

dateNow	back to summary
public LocalDate dateNow(ZoneId zone) Overrides default java.time.chrono.Chronology.dateNow. Obtains the current ISO local date from the system clock in the specified time-zone. This will query the `system clock` to obtain the current date. Specifying the time-zone avoids dependence on the default time-zone. Using this method will prevent the ability to use an alternate clock for testing because the clock is hard-coded. Parameters zone:ZoneId Doc from java.time.chrono.Chronology.dateNow. the zone ID to use, not null Returns:LocalDate the current ISO local date using the system clock, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public LocalDate dateNow(ZoneId zone)

Overrides default java.time.chrono.Chronology.dateNow.

Obtains the current ISO local date from the system clock in the specified time-zone.

This will query the system clock to obtain the current date. Specifying the time-zone avoids dependence on the default time-zone.

Using this method will prevent the ability to use an alternate clock for testing because the clock is hard-coded.

Parameters

zone:ZoneId

Doc from java.time.chrono.Chronology.dateNow.

the zone ID to use, not null

Returns:LocalDate

the current ISO local date using the system clock, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateNow back to summary

dateNow	back to summary
public LocalDate dateNow(Clock clock) Overrides default java.time.chrono.Chronology.dateNow. Obtains the current ISO local date from the specified clock. This will query the specified clock to obtain the current date - today. Using this method allows the use of an alternate clock for testing. The alternate clock may be introduced using `dependency injection`. Parameters clock:Clock the clock to use, not null Returns:LocalDate the current ISO local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public LocalDate dateNow(Clock clock)

Overrides default java.time.chrono.Chronology.dateNow.

Obtains the current ISO local date from the specified clock.

This will query the specified clock to obtain the current date - today. Using this method allows the use of an alternate clock for testing. The alternate clock may be introduced using dependency injection.

Parameters

clock:Clock: the clock to use, not null

Returns:LocalDate

the current ISO local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateYearDay	back to summary
public LocalDate dateYearDay(Era era, int yearOfEra, int dayOfYear) Overrides default java.time.chrono.Chronology.dateYearDay. Obtains an ISO local date from the era, year-of-era and day-of-year fields. Parameters era:Era the ISO era, not null yearOfEra:int the ISO year-of-era dayOfYear:int the ISO day-of-year Returns:LocalDate the ISO local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

dateYearDay

back to summary

public LocalDate dateYearDay(Era era, int yearOfEra, int dayOfYear)

Overrides default java.time.chrono.Chronology.dateYearDay.

Obtains an ISO local date from the era, year-of-era and day-of-year fields.

Parameters

era:Era: the ISO era, not null
yearOfEra:int: the ISO year-of-era
dayOfYear:int: the ISO day-of-year

Returns:LocalDate

the ISO local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateYearDay back to summary

dateYearDay	back to summary
public LocalDate dateYearDay(int prolepticYear, int dayOfYear) Implements java.time.chrono.Chronology.dateYearDay. Obtains an ISO local date from the proleptic-year and day-of-year fields. This is equivalent to `LocalDate#ofYearDay(int, int)`. Parameters prolepticYear:int the ISO proleptic-year dayOfYear:int the ISO day-of-year Returns:LocalDate the ISO local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public LocalDate dateYearDay(int prolepticYear, int dayOfYear)

Implements java.time.chrono.Chronology.dateYearDay.

Obtains an ISO local date from the proleptic-year and day-of-year fields.

This is equivalent to LocalDate#ofYearDay(int, int).

Parameters

prolepticYear:int: the ISO proleptic-year
dayOfYear:int: the ISO day-of-year

Returns:LocalDate

the ISO local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

epochSecond	back to summary
public long epochSecond(int prolepticYear, int month, int dayOfMonth, int hour, int minute, int second, ZoneOffset zoneOffset) Overrides default java.time.chrono.Chronology.epochSecond. Gets the number of seconds from the epoch of 1970-01-01T00:00:00Z. The number of seconds is calculated using the year, month, day-of-month, hour, minute, second, and zoneOffset. Parameters prolepticYear:int the year, from MIN_YEAR to MAX_YEAR month:int the month-of-year, from 1 to 12 dayOfMonth:int the day-of-month, from 1 to 31 hour:int the hour-of-day, from 0 to 23 minute:int the minute-of-hour, from 0 to 59 second:int the second-of-minute, from 0 to 59 zoneOffset:ZoneOffset the zone offset, not null Returns:long the number of seconds relative to 1970-01-01T00:00:00Z, may be negative Annotations @Override Exceptions DateTimeException: if the value of any argument is out of range, or if the day-of-month is invalid for the month-of-year Since 9

epochSecond

back to summary

public long epochSecond(int prolepticYear, int month, int dayOfMonth, int hour, int minute, int second, ZoneOffset zoneOffset)

Overrides default java.time.chrono.Chronology.epochSecond.

Gets the number of seconds from the epoch of 1970-01-01T00:00:00Z.

The number of seconds is calculated using the year, month, day-of-month, hour, minute, second, and zoneOffset.

Parameters

prolepticYear:int: the year, from MIN_YEAR to MAX_YEAR
month:int: the month-of-year, from 1 to 12
dayOfMonth:int: the day-of-month, from 1 to 31
hour:int: the hour-of-day, from 0 to 23
minute:int: the minute-of-hour, from 0 to 59
second:int: the second-of-minute, from 0 to 59
zoneOffset:ZoneOffset: the zone offset, not null

Returns:long

the number of seconds relative to 1970-01-01T00:00:00Z, may be negative

Annotations

@Override

Exceptions

DateTimeException:: if the value of any argument is out of range, or if the day-of-month is invalid for the month-of-year

Since

eraOf	back to summary
public IsoEra eraOf(int eraValue) Implements java.time.chrono.Chronology.eraOf. Doc from java.time.chrono.Chronology.eraOf. Creates the chronology era object from the numeric value. The era is, conceptually, the largest division of the time-line. Most calendar systems have a single epoch dividing the time-line into two eras. However, some have multiple eras, such as one for the reign of each leader. The exact meaning is determined by the chronology according to the following constraints. The era in use at 1970-01-01 must have the value 1. Later eras must have sequentially higher values. Earlier eras must have sequentially lower values. Each chronology must refer to an enum or similar singleton to provide the era values. This method returns the singleton era of the correct type for the specified era value. Parameters eraValue:int the era value Returns:IsoEra the calendar system era, not null Annotations @Override

eraOf

back to summary

public IsoEra eraOf(int eraValue)

Implements java.time.chrono.Chronology.eraOf.

Doc from java.time.chrono.Chronology.eraOf.

Creates the chronology era object from the numeric value.

The era is, conceptually, the largest division of the time-line. Most calendar systems have a single epoch dividing the time-line into two eras. However, some have multiple eras, such as one for the reign of each leader. The exact meaning is determined by the chronology according to the following constraints.

The era in use at 1970-01-01 must have the value 1. Later eras must have sequentially higher values. Earlier eras must have sequentially lower values. Each chronology must refer to an enum or similar singleton to provide the era values.

This method returns the singleton era of the correct type for the specified era value.

Parameters

eraValue:int: the era value

Returns:IsoEra

the calendar system era, not null

Annotations

@Override

eras	back to summary
public List<Era> eras() Implements java.time.chrono.Chronology.eras. Doc from java.time.chrono.Chronology.eras. Gets the list of eras for the chronology. Most calendar systems have an era, within which the year has meaning. If the calendar system does not support the concept of eras, an empty list must be returned. Returns:List<Era> the list of eras for the chronology, may be immutable, not null Annotations @Override

eras

back to summary

public List<Era> eras()

Implements java.time.chrono.Chronology.eras.

Doc from java.time.chrono.Chronology.eras.

Gets the list of eras for the chronology.

Most calendar systems have an era, within which the year has meaning. If the calendar system does not support the concept of eras, an empty list must be returned.

Returns:List<Era>

the list of eras for the chronology, may be immutable, not null

Annotations

@Override

getCalendarType back to summary

getCalendarType	back to summary
public String getCalendarType() Implements java.time.chrono.Chronology.getCalendarType. Gets the calendar type of the underlying calendar system - 'iso8601'. The calendar type is an identifier defined by the Unicode Locale Data Markup Language (LDML) specification. It can be used to lookup the `Chronology` using `Chronology#of(String)`. It can also be used as part of a locale, accessible via `Locale#getUnicodeLocaleType(String)` with the key 'ca'. Returns:String the calendar system type - 'iso8601' Annotations @Override See Also `getId()`

public String getCalendarType()

Implements java.time.chrono.Chronology.getCalendarType.

Gets the calendar type of the underlying calendar system - 'iso8601'.

The calendar type is an identifier defined by the Unicode Locale Data Markup Language (LDML) specification. It can be used to lookup the Chronology using Chronology#of(String). It can also be used as part of a locale, accessible via Locale#getUnicodeLocaleType(String) with the key 'ca'.

Returns:String

the calendar system type - 'iso8601'

Annotations

@Override

See Also

getId()

getId back to summary

getId	back to summary
public String getId() Implements java.time.chrono.Chronology.getId. Gets the ID of the chronology - 'ISO'. The ID uniquely identifies the `Chronology`. It can be used to lookup the `Chronology` using `Chronology#of(String)`. Returns:String the chronology ID - 'ISO' Annotations @Override See Also `getCalendarType()`

public String getId()

Implements java.time.chrono.Chronology.getId.

Gets the ID of the chronology - 'ISO'.

The ID uniquely identifies the Chronology. It can be used to lookup the Chronology using Chronology#of(String).

Returns:String

the chronology ID - 'ISO'

Annotations

@Override

See Also

getCalendarType()

isIsoBased back to summary

isIsoBased	back to summary
public boolean isIsoBased() Overrides default java.time.chrono.Chronology.isIsoBased. `IsoChronology` is an ISO based chronology, which supports fields in `IsoFields`, such as `DAY_OF_QUARTER` and `QUARTER_OF_YEAR`. Returns:boolean `true` Annotations @Override Since 19 See Also `IsoFields`

public boolean isIsoBased()

Overrides default java.time.chrono.Chronology.isIsoBased.

IsoChronology is an ISO based chronology, which supports fields in IsoFields, such as DAY_OF_QUARTER and QUARTER_OF_YEAR.

Returns:boolean

true

Annotations

@Override

Since

See Also

IsoFields

isLeapYear	back to summary
public boolean isLeapYear(long prolepticYear) Implements java.time.chrono.Chronology.isLeapYear. Checks if the year is a leap year, according to the ISO proleptic calendar system rules. This method applies the current rules for leap years across the whole time-line. In general, a year is a leap year if it is divisible by four without remainder. However, years divisible by 100, are not leap years, with the exception of years divisible by 400 which are. For example, 1904 is a leap year it is divisible by 4. 1900 was not a leap year as it is divisible by 100, however 2000 was a leap year as it is divisible by 400. The calculation is proleptic - applying the same rules into the far future and far past. This is historically inaccurate, but is correct for the ISO-8601 standard. Parameters prolepticYear:long the ISO proleptic year to check Returns:boolean true if the year is leap, false otherwise Annotations @Override

isLeapYear

back to summary

public boolean isLeapYear(long prolepticYear)

Implements java.time.chrono.Chronology.isLeapYear.

Checks if the year is a leap year, according to the ISO proleptic calendar system rules.

This method applies the current rules for leap years across the whole time-line. In general, a year is a leap year if it is divisible by four without remainder. However, years divisible by 100, are not leap years, with the exception of years divisible by 400 which are.

For example, 1904 is a leap year it is divisible by 4. 1900 was not a leap year as it is divisible by 100, however 2000 was a leap year as it is divisible by 400.

The calculation is proleptic - applying the same rules into the far future and far past. This is historically inaccurate, but is correct for the ISO-8601 standard.

Parameters

prolepticYear:long: the ISO proleptic year to check

Returns:boolean

true if the year is leap, false otherwise

Annotations

@Override

localDateTime back to summary

localDateTime	back to summary
public LocalDateTime localDateTime(TemporalAccessor temporal) Overrides default java.time.chrono.Chronology.localDateTime. Obtains an ISO local date-time from another date-time object. This is equivalent to `LocalDateTime#from(TemporalAccessor)`. Parameters temporal:TemporalAccessor the date-time object to convert, not null Returns:LocalDateTime the ISO local date-time, not null Annotations @Override Exceptions DateTimeException: if unable to create the date-time

public LocalDateTime localDateTime(TemporalAccessor temporal)

Overrides default java.time.chrono.Chronology.localDateTime.

Obtains an ISO local date-time from another date-time object.

This is equivalent to LocalDateTime#from(TemporalAccessor).

Parameters

temporal:TemporalAccessor: the date-time object to convert, not null

Returns:LocalDateTime

the ISO local date-time, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date-time

numberOfDaysOfMonth	back to summary
private int numberOfDaysOfMonth(int year, int month) Gets the number of days for the given month in the given year. Parameters year:int the year to represent, from MIN_YEAR to MAX_YEAR month:int the month-of-year to represent, from 1 to 12 Returns:int the number of days for the given month in the given year

numberOfDaysOfMonth

back to summary

private int numberOfDaysOfMonth(int year, int month)

Gets the number of days for the given month in the given year.

Parameters

year:int: the year to represent, from MIN_YEAR to MAX_YEAR
month:int: the month-of-year to represent, from 1 to 12

Returns:int

the number of days for the given month in the given year

period back to summary

period	back to summary
public Period period(int years, int months, int days) Overrides default java.time.chrono.Chronology.period. Obtains a period for this chronology based on years, months and days. This returns a period tied to the ISO chronology using the specified years, months and days. See `Period` for further details. Parameters years:int the number of years, may be negative months:int the number of years, may be negative days:int the number of years, may be negative Returns:Period the ISO period, not null Annotations @Override

public Period period(int years, int months, int days)

Overrides default java.time.chrono.Chronology.period.

Obtains a period for this chronology based on years, months and days.

This returns a period tied to the ISO chronology using the specified years, months and days. See Period for further details.

Parameters

years:int: the number of years, may be negative
months:int: the number of years, may be negative
days:int: the number of years, may be negative

Returns:Period

the ISO period, not null

Annotations

@Override

prolepticYear back to summary

prolepticYear	back to summary
public int prolepticYear(Era era, int yearOfEra) Implements java.time.chrono.Chronology.prolepticYear. Doc from java.time.chrono.Chronology.prolepticYear. Calculates the proleptic-year given the era and year-of-era. This combines the era and year-of-era into the single proleptic-year field. If the chronology makes active use of eras, such as `JapaneseChronology` then the year-of-era will be validated against the era. For other chronologies, validation is optional. Parameters era:Era the era of the correct type for the chronology, not null yearOfEra:int the chronology year-of-era Returns:int the proleptic-year Annotations @Override

public int prolepticYear(Era era, int yearOfEra)

Implements java.time.chrono.Chronology.prolepticYear.

Doc from java.time.chrono.Chronology.prolepticYear.

Calculates the proleptic-year given the era and year-of-era.

This combines the era and year-of-era into the single proleptic-year field.

If the chronology makes active use of eras, such as JapaneseChronology then the year-of-era will be validated against the era. For other chronologies, validation is optional.

Parameters

era:Era: the era of the correct type for the chronology, not null
yearOfEra:int: the chronology year-of-era

Returns:int

the proleptic-year

Annotations

@Override

range back to summary

range	back to summary
public ValueRange range(ChronoField field) Implements java.time.chrono.Chronology.range. Doc from java.time.chrono.Chronology.range. Gets the range of valid values for the specified field. All fields can be expressed as a `long` integer. This method returns an object that describes the valid range for that value. Note that the result only describes the minimum and maximum valid values and it is important not to read too much into them. For example, there could be values within the range that are invalid for the field. This method will return a result whether or not the chronology supports the field. Parameters field:ChronoField the field to get the range for, not null Returns:ValueRange the range of valid values for the field, not null Annotations @Override

public ValueRange range(ChronoField field)

Implements java.time.chrono.Chronology.range.

Doc from java.time.chrono.Chronology.range.

Gets the range of valid values for the specified field.

All fields can be expressed as a long integer. This method returns an object that describes the valid range for that value.

Note that the result only describes the minimum and maximum valid values and it is important not to read too much into them. For example, there could be values within the range that are invalid for the field.

This method will return a result whether or not the chronology supports the field.

Parameters

field:ChronoField: the field to get the range for, not null

Returns:ValueRange

the range of valid values for the field, not null

Annotations

@Override

readObject	back to summary
private void readObject(ObjectInputStream s) throws InvalidObjectException Hides java.time.chrono.AbstractChronology.readObject. Defend against malicious streams. Parameters s:ObjectInputStream the stream to read Annotations @Serial Exceptions InvalidObjectException: always

readObject

back to summary

private void readObject(ObjectInputStream s) throws InvalidObjectException

Hides java.time.chrono.AbstractChronology.readObject.

Defend against malicious streams.

Parameters

s:ObjectInputStream: the stream to read

Annotations

@Serial

Exceptions

InvalidObjectException:: always

resolveDate back to summary

resolveDate	back to summary
public LocalDate resolveDate(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveDate. Implements java.time.chrono.Chronology.resolveDate. Resolves parsed `ChronoField` values into a date during parsing. Most `TemporalField` implementations are resolved using the resolve method on the field. By contrast, the `ChronoField` class defines fields that only have meaning relative to the chronology. As such, `ChronoField` date fields are resolved here in the context of a specific chronology. `ChronoField` instances on the ISO calendar system are resolved as follows. `EPOCH_DAY` - If present, this is converted to a `LocalDate` and all other date fields are then cross-checked against the date. `PROLEPTIC_MONTH` - If present, then it is split into the `YEAR` and `MONTH_OF_YEAR`. If the mode is strict or smart then the field is validated. `YEAR_OF_ERA` and `ERA` - If both are present, then they are combined to form a `YEAR`. In lenient mode, the `YEAR_OF_ERA` range is not validated, in smart and strict mode it is. The `ERA` is validated for range in all three modes. If only the `YEAR_OF_ERA` is present, and the mode is smart or lenient, then the current era (CE/AD) is assumed. In strict mode, no era is assumed and the `YEAR_OF_ERA` is left untouched. If only the `ERA` is present, then it is left untouched. `YEAR`, `MONTH_OF_YEAR` and `DAY_OF_MONTH` - If all three are present, then they are combined to form a `LocalDate`. In all three modes, the `YEAR` is validated. If the mode is smart or strict, then the month and day are validated, with the day validated from 1 to 31. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first of January in the requested year, then adding the difference in months, then the difference in days. If the mode is smart, and the day-of-month is greater than the maximum for the year-month, then the day-of-month is adjusted to the last day-of-month. If the mode is strict, then the three fields must form a valid date. `YEAR` and `DAY_OF_YEAR` - If both are present, then they are combined to form a `LocalDate`. In all three modes, the `YEAR` is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first of January in the requested year, then adding the difference in days. If the mode is smart or strict, then the two fields must form a valid date. `YEAR`, `MONTH_OF_YEAR`, `ALIGNED_WEEK_OF_MONTH` and `ALIGNED_DAY_OF_WEEK_IN_MONTH` - If all four are present, then they are combined to form a `LocalDate`. In all three modes, the `YEAR` is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first of January in the requested year, then adding the difference in months, then the difference in weeks, then in days. If the mode is smart or strict, then the all four fields are validated to their outer ranges. The date is then combined in a manner equivalent to creating a date on the first day of the requested year and month, then adding the amount in weeks and days to reach their values. If the mode is strict, the date is additionally validated to check that the day and week adjustment did not change the month. `YEAR`, `MONTH_OF_YEAR`, `ALIGNED_WEEK_OF_MONTH` and `DAY_OF_WEEK` - If all four are present, then they are combined to form a `LocalDate`. The approach is the same as described above for years, months and weeks in `ALIGNED_DAY_OF_WEEK_IN_MONTH`. The day-of-week is adjusted as the next or same matching day-of-week once the years, months and weeks have been handled. `YEAR`, `ALIGNED_WEEK_OF_YEAR` and `ALIGNED_DAY_OF_WEEK_IN_YEAR` - If all three are present, then they are combined to form a `LocalDate`. In all three modes, the `YEAR` is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first of January in the requested year, then adding the difference in weeks, then in days. If the mode is smart or strict, then the all three fields are validated to their outer ranges. The date is then combined in a manner equivalent to creating a date on the first day of the requested year, then adding the amount in weeks and days to reach their values. If the mode is strict, the date is additionally validated to check that the day and week adjustment did not change the year. `YEAR`, `ALIGNED_WEEK_OF_YEAR` and `DAY_OF_WEEK` - If all three are present, then they are combined to form a `LocalDate`. The approach is the same as described above for years and weeks in `ALIGNED_DAY_OF_WEEK_IN_YEAR`. The day-of-week is adjusted as the next or same matching day-of-week once the years and weeks have been handled. Parameters fieldValues:Map<TemporalField, Long> the map of fields to values, which can be updated, not null resolverStyle:ResolverStyle the requested type of resolve, not null Returns:LocalDate the resolved date, null if insufficient information to create a date Annotations @Override Exceptions DateTimeException: if the date cannot be resolved, typically because of a conflict in the input data

public LocalDate resolveDate(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle)

Overrides java.time.chrono.AbstractChronology.resolveDate.

Implements java.time.chrono.Chronology.resolveDate.

Resolves parsed ChronoField values into a date during parsing.

Most TemporalField implementations are resolved using the resolve method on the field. By contrast, the ChronoField class defines fields that only have meaning relative to the chronology. As such, ChronoField date fields are resolved here in the context of a specific chronology.

ChronoField instances on the ISO calendar system are resolved as follows.

EPOCH_DAY - If present, this is converted to a LocalDate and all other date fields are then cross-checked against the date.
PROLEPTIC_MONTH - If present, then it is split into the YEAR and MONTH_OF_YEAR. If the mode is strict or smart then the field is validated.
YEAR_OF_ERA and ERA - If both are present, then they are combined to form a YEAR. In lenient mode, the YEAR_OF_ERA range is not validated, in smart and strict mode it is. The ERA is validated for range in all three modes. If only the YEAR_OF_ERA is present, and the mode is smart or lenient, then the current era (CE/AD) is assumed. In strict mode, no era is assumed and the YEAR_OF_ERA is left untouched. If only the ERA is present, then it is left untouched.
YEAR, MONTH_OF_YEAR and DAY_OF_MONTH - If all three are present, then they are combined to form a LocalDate. In all three modes, the YEAR is validated. If the mode is smart or strict, then the month and day are validated, with the day validated from 1 to 31. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first of January in the requested year, then adding the difference in months, then the difference in days. If the mode is smart, and the day-of-month is greater than the maximum for the year-month, then the day-of-month is adjusted to the last day-of-month. If the mode is strict, then the three fields must form a valid date.
YEAR and DAY_OF_YEAR - If both are present, then they are combined to form a LocalDate. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first of January in the requested year, then adding the difference in days. If the mode is smart or strict, then the two fields must form a valid date.
YEAR, MONTH_OF_YEAR, ALIGNED_WEEK_OF_MONTH and ALIGNED_DAY_OF_WEEK_IN_MONTH - If all four are present, then they are combined to form a LocalDate. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first of January in the requested year, then adding the difference in months, then the difference in weeks, then in days. If the mode is smart or strict, then the all four fields are validated to their outer ranges. The date is then combined in a manner equivalent to creating a date on the first day of the requested year and month, then adding the amount in weeks and days to reach their values. If the mode is strict, the date is additionally validated to check that the day and week adjustment did not change the month.
YEAR, MONTH_OF_YEAR, ALIGNED_WEEK_OF_MONTH and DAY_OF_WEEK - If all four are present, then they are combined to form a LocalDate. The approach is the same as described above for years, months and weeks in ALIGNED_DAY_OF_WEEK_IN_MONTH. The day-of-week is adjusted as the next or same matching day-of-week once the years, months and weeks have been handled.
YEAR, ALIGNED_WEEK_OF_YEAR and ALIGNED_DAY_OF_WEEK_IN_YEAR - If all three are present, then they are combined to form a LocalDate. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first of January in the requested year, then adding the difference in weeks, then in days. If the mode is smart or strict, then the all three fields are validated to their outer ranges. The date is then combined in a manner equivalent to creating a date on the first day of the requested year, then adding the amount in weeks and days to reach their values. If the mode is strict, the date is additionally validated to check that the day and week adjustment did not change the year.
YEAR, ALIGNED_WEEK_OF_YEAR and DAY_OF_WEEK - If all three are present, then they are combined to form a LocalDate. The approach is the same as described above for years and weeks in ALIGNED_DAY_OF_WEEK_IN_YEAR. The day-of-week is adjusted as the next or same matching day-of-week once the years and weeks have been handled.

Parameters

fieldValues:Map<TemporalField, Long>: the map of fields to values, which can be updated, not null
resolverStyle:ResolverStyle: the requested type of resolve, not null

Returns:LocalDate

the resolved date, null if insufficient information to create a date

Annotations

@Override

Exceptions

DateTimeException:: if the date cannot be resolved, typically because of a conflict in the input data

resolveProlepticMonth	back to summary
pack-priv void resolveProlepticMonth(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveProlepticMonth. Annotations @Override

resolveProlepticMonth

back to summary

pack-priv void resolveProlepticMonth(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle)

Overrides java.time.chrono.AbstractChronology.resolveProlepticMonth.

Annotations

@Override

resolveYearOfEra	back to summary
pack-priv LocalDate resolveYearOfEra(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveYearOfEra. Annotations @Override

resolveYearOfEra

back to summary

pack-priv LocalDate resolveYearOfEra(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle)

Overrides java.time.chrono.AbstractChronology.resolveYearOfEra.

Annotations

@Override

resolveYMD	back to summary
pack-priv LocalDate resolveYMD(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveYMD. Annotations @Override

resolveYMD

back to summary

pack-priv LocalDate resolveYMD(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle)

Overrides java.time.chrono.AbstractChronology.resolveYMD.

Annotations

@Override

writeReplace back to summary

writeReplace	back to summary
pack-priv Object writeReplace() Overrides java.time.chrono.AbstractChronology.writeReplace. Writes the Chronology using a dedicated serialized form. Returns:Object the instance of `Ser`, not null Annotations @Override @Serial Serial data out.writeByte(1); // identifies a Chronology out.writeUTF(getId());

pack-priv Object writeReplace()

Overrides java.time.chrono.AbstractChronology.writeReplace.

Writes the Chronology using a dedicated serialized form.

Returns:Object

the instance of Ser, not null

Annotations

@Override
@Serial

Serial data

 out.writeByte(1);     // identifies a Chronology
 out.writeUTF(getId());

zonedDateTime back to summary

zonedDateTime	back to summary
public ZonedDateTime zonedDateTime(TemporalAccessor temporal) Overrides default java.time.chrono.Chronology.zonedDateTime. Obtains an ISO zoned date-time from another date-time object. This is equivalent to `ZonedDateTime#from(TemporalAccessor)`. Parameters temporal:TemporalAccessor the date-time object to convert, not null Returns:ZonedDateTime the ISO zoned date-time, not null Annotations @Override Exceptions DateTimeException: if unable to create the date-time

public ZonedDateTime zonedDateTime(TemporalAccessor temporal)

Overrides default java.time.chrono.Chronology.zonedDateTime.

Obtains an ISO zoned date-time from another date-time object.

This is equivalent to ZonedDateTime#from(TemporalAccessor).

Parameters

temporal:TemporalAccessor: the date-time object to convert, not null

Returns:ZonedDateTime

the ISO zoned date-time, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date-time

zonedDateTime back to summary

zonedDateTime	back to summary
public ZonedDateTime zonedDateTime(Instant instant, ZoneId zone) Overrides default java.time.chrono.Chronology.zonedDateTime. Obtains an ISO zoned date-time in this chronology from an `Instant`. This is equivalent to `ZonedDateTime#ofInstant(Instant, ZoneId)`. Parameters instant:Instant the instant to create the date-time from, not null zone:ZoneId the time-zone, not null Returns:ZonedDateTime the zoned date-time, not null Annotations @Override Exceptions DateTimeException: if the result exceeds the supported range

public ZonedDateTime zonedDateTime(Instant instant, ZoneId zone)

Overrides default java.time.chrono.Chronology.zonedDateTime.

Obtains an ISO zoned date-time in this chronology from an Instant.

This is equivalent to ZonedDateTime#ofInstant(Instant, ZoneId).

Parameters