ThreeTen-Extra 1.8.0 · org.threeten.extra.chrono.EthiopicChronology

Modifier and Type	Field and Description
public static final EthiopicChronology	INSTANCE Singleton instance for the Ethiopic chronology.
private static final long	serialVersionUID Serialization version.

Access	Constructor and Description
public	EthiopicChronology() Deprecated Use the singleton `INSTANCE` instead. Private constructor, that is public to satisfy the `ServiceLoader`.

Method Summary

Modifier and Type	Method and Description
public EthiopicDate	Returns: the Ethiopic local date, not null date(Era the Ethiopic era, not null era, int the year-of-era yearOfEra, int the month-of-year month, int the day-of-month dayOfMonth) Overrides default java.time.chrono.Chronology.date. Obtains a local date in Ethiopic calendar system from the era, year-of-era, month-of-year and day-of-month fields.
public EthiopicDate	Returns: the Ethiopic local date, not null date(int the proleptic-year prolepticYear, int the month-of-year month, int the day-of-month dayOfMonth) Implements java.time.chrono.Chronology.date. Obtains a local date in Ethiopic calendar system from the proleptic-year, month-of-year and day-of-month fields.
public EthiopicDate	Returns: the Ethiopic local date, not null date(TemporalAccessor the date-time object to convert, not null temporal) Implements java.time.chrono.Chronology.date. Obtains a Ethiopic local date from another date-time object.
public EthiopicDate	Returns: the Ethiopic local date, not null dateEpochDay(long the epoch day epochDay) Implements java.time.chrono.Chronology.dateEpochDay. Obtains a local date in the Ethiopic calendar system from the epoch-day.
public EthiopicDate	Returns: the current Ethiopic local date using the system clock and default time-zone, not null dateNow() Overrides default java.time.chrono.Chronology.dateNow. Obtains the current Ethiopic local date from the system clock in the default time-zone.
public EthiopicDate	Returns: the current Ethiopic 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 Ethiopic local date from the system clock in the specified time-zone.
public EthiopicDate	Returns: the current Ethiopic local date, not null dateNow(Clock the clock to use, not null clock) Overrides default java.time.chrono.Chronology.dateNow. Obtains the current Ethiopic local date from the specified clock.
public EthiopicDate	Returns: the Ethiopic local date, not null dateYearDay(Era the Ethiopic era, not null era, int the year-of-era yearOfEra, int the day-of-year dayOfYear) Overrides default java.time.chrono.Chronology.dateYearDay. Obtains a local date in Ethiopic calendar system from the era, year-of-era and day-of-year fields.
public EthiopicDate	Returns: the Ethiopic local date, not null dateYearDay(int the proleptic-year prolepticYear, int the day-of-year dayOfYear) Implements java.time.chrono.Chronology.dateYearDay. Obtains a local date in Ethiopic calendar system from the proleptic-year and day-of-year fields.
public EthiopicEra	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 - 'ethiopic' getCalendarType() Implements java.time.chrono.Chronology.getCalendarType. Gets the calendar type of the underlying calendar system - 'ethiopic'.
public String	Returns: the chronology ID - 'Ethiopic' getId() Implements java.time.chrono.Chronology.getId. Gets the ID of the chronology - 'Ethiopic'.
public ChronoLocalDateTime<EthiopicDate>	Returns: the Ethiopic local date-time, not null localDateTime(TemporalAccessor the date-time object to convert, not null temporal) Overrides default java.time.chrono.Chronology.localDateTime. Obtains a Ethiopic local date-time from another date-time object.
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.
private Object	Returns: the singleton instance, not null readResolve() Resolve singleton.
public EthiopicDate	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.
public ChronoZonedDateTime<EthiopicDate>	Returns: the Ethiopic zoned date-time, not null zonedDateTime(TemporalAccessor the date-time object to convert, not null temporal) Overrides default java.time.chrono.Chronology.zonedDateTime. Obtains a Ethiopic zoned date-time from another date-time object.
public ChronoZonedDateTime<EthiopicDate>	Returns: the Ethiopic 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 a Ethiopic zoned date-time in this chronology from an `Instant`.

Inherited from org.threeten.extra.chrono.AbstractNileChronology:: isLeapYear range

INSTANCE	back to summary
public static final EthiopicChronology INSTANCE Singleton instance for the Ethiopic chronology.

serialVersionUID	back to summary
private static final long serialVersionUID Serialization version.

EthiopicChronology	back to summary
public EthiopicChronology() Deprecated Use the singleton `INSTANCE` instead. Private constructor, that is public to satisfy the `ServiceLoader`. Annotations @Deprecated

Method Detail

date back to summary

date	back to summary
public EthiopicDate date(Era era, int yearOfEra, int month, int dayOfMonth) Overrides default java.time.chrono.Chronology.date. Obtains a local date in Ethiopic calendar system from the era, year-of-era, month-of-year and day-of-month fields. Parameters era:Era the Ethiopic era, not null yearOfEra:int the year-of-era month:int the month-of-year dayOfMonth:int the day-of-month Returns:EthiopicDate the Ethiopic local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date ClassCastException: if the `era` is not a `EthiopicEra`

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

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

Obtains a local date in Ethiopic calendar system from the era, year-of-era, month-of-year and day-of-month fields.

Parameters

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

Returns:EthiopicDate

the Ethiopic local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date
ClassCastException:: if the era is not a EthiopicEra

date	back to summary
public EthiopicDate date(int prolepticYear, int month, int dayOfMonth) Implements java.time.chrono.Chronology.date. Obtains a local date in Ethiopic calendar system from the proleptic-year, month-of-year and day-of-month fields. Parameters prolepticYear:int the proleptic-year month:int the month-of-year dayOfMonth:int the day-of-month Returns:EthiopicDate the Ethiopic local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

date

back to summary

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

Implements java.time.chrono.Chronology.date.

Obtains a local date in Ethiopic calendar system from the proleptic-year, month-of-year and day-of-month fields.

Parameters

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

Returns:EthiopicDate

the Ethiopic local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

date	back to summary
public EthiopicDate date(TemporalAccessor temporal) Implements java.time.chrono.Chronology.date. Obtains a Ethiopic local date from another date-time object. Parameters temporal:TemporalAccessor the date-time object to convert, not null Returns:EthiopicDate the Ethiopic local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

date

back to summary

public EthiopicDate date(TemporalAccessor temporal)

Implements java.time.chrono.Chronology.date.

Obtains a Ethiopic local date from another date-time object.

Parameters

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

Returns:EthiopicDate

the Ethiopic local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateEpochDay	back to summary
public EthiopicDate dateEpochDay(long epochDay) Implements java.time.chrono.Chronology.dateEpochDay. Obtains a local date in the Ethiopic calendar system from the epoch-day. Parameters epochDay:long the epoch day Returns:EthiopicDate the Ethiopic local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

dateEpochDay

back to summary

public EthiopicDate dateEpochDay(long epochDay)

Implements java.time.chrono.Chronology.dateEpochDay.

Obtains a local date in the Ethiopic calendar system from the epoch-day.

Parameters

epochDay:long: the epoch day

Returns:EthiopicDate

the Ethiopic local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateNow back to summary

dateNow	back to summary
public EthiopicDate dateNow() Overrides default java.time.chrono.Chronology.dateNow. Obtains the current Ethiopic 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:EthiopicDate the current Ethiopic local date using the system clock and default time-zone, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public EthiopicDate dateNow()

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

Obtains the current Ethiopic 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:EthiopicDate

the current Ethiopic 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 EthiopicDate dateNow(ZoneId zone) Overrides default java.time.chrono.Chronology.dateNow. Obtains the current Ethiopic 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 the zone ID to use, not null Returns:EthiopicDate the current Ethiopic local date using the system clock, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public EthiopicDate dateNow(ZoneId zone)

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

Obtains the current Ethiopic 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: the zone ID to use, not null

Returns:EthiopicDate

the current Ethiopic 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 EthiopicDate dateNow(Clock clock) Overrides default java.time.chrono.Chronology.dateNow. Obtains the current Ethiopic 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:EthiopicDate the current Ethiopic local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

public EthiopicDate dateNow(Clock clock)

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

Obtains the current Ethiopic 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:EthiopicDate

the current Ethiopic local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

dateYearDay back to summary

dateYearDay	back to summary
public EthiopicDate dateYearDay(Era era, int yearOfEra, int dayOfYear) Overrides default java.time.chrono.Chronology.dateYearDay. Obtains a local date in Ethiopic calendar system from the era, year-of-era and day-of-year fields. Parameters era:Era the Ethiopic era, not null yearOfEra:int the year-of-era dayOfYear:int the day-of-year Returns:EthiopicDate the Ethiopic local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date ClassCastException: if the `era` is not a `EthiopicEra`

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

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

Obtains a local date in Ethiopic calendar system from the era, year-of-era and day-of-year fields.

Parameters

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

Returns:EthiopicDate

the Ethiopic local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date
ClassCastException:: if the era is not a EthiopicEra

dateYearDay	back to summary
public EthiopicDate dateYearDay(int prolepticYear, int dayOfYear) Implements java.time.chrono.Chronology.dateYearDay. Obtains a local date in Ethiopic calendar system from the proleptic-year and day-of-year fields. Parameters prolepticYear:int the proleptic-year dayOfYear:int the day-of-year Returns:EthiopicDate the Ethiopic local date, not null Annotations @Override Exceptions DateTimeException: if unable to create the date

dateYearDay

back to summary

public EthiopicDate dateYearDay(int prolepticYear, int dayOfYear)

Implements java.time.chrono.Chronology.dateYearDay.

Obtains a local date in Ethiopic calendar system from the proleptic-year and day-of-year fields.

Parameters

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

Returns:EthiopicDate

the Ethiopic local date, not null

Annotations

@Override

Exceptions

DateTimeException:: if unable to create the date

eraOf	back to summary
public EthiopicEra 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:EthiopicEra the calendar system era, not null Annotations @Override

eraOf

back to summary

public EthiopicEra 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:EthiopicEra

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 - 'ethiopic'. 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 - 'ethiopic' Annotations @Override See Also `getId()`

public String getCalendarType()

Implements java.time.chrono.Chronology.getCalendarType.

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

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 - 'ethiopic'

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 - 'Ethiopic'. The ID uniquely identifies the `Chronology`. It can be used to lookup the `Chronology` using `Chronology#of(String)`. Returns:String the chronology ID - 'Ethiopic' Annotations @Override See Also `getCalendarType()`

public String getId()

Implements java.time.chrono.Chronology.getId.

Gets the ID of the chronology - 'Ethiopic'.

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

Returns:String

the chronology ID - 'Ethiopic'

Annotations

@Override

See Also

getCalendarType()

localDateTime	back to summary
public ChronoLocalDateTime<EthiopicDate> localDateTime(TemporalAccessor temporal) Overrides default java.time.chrono.Chronology.localDateTime. Obtains a Ethiopic local date-time from another date-time object. Parameters temporal:TemporalAccessor the date-time object to convert, not null Returns:ChronoLocalDateTime<EthiopicDate> the Ethiopic local date-time, not null Annotations @Override @SuppressWarnings:unchecked Exceptions DateTimeException: if unable to create the date-time

localDateTime

back to summary

public ChronoLocalDateTime<EthiopicDate> localDateTime(TemporalAccessor temporal)

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

Obtains a Ethiopic local date-time from another date-time object.

Parameters

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

Returns:ChronoLocalDateTime<EthiopicDate>

the Ethiopic local date-time, not null

Annotations

@Override
@SuppressWarnings:unchecked

Exceptions

DateTimeException:: if unable to create the date-time

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

readResolve	back to summary
private Object readResolve() Resolve singleton. Returns:Object the singleton instance, not null

readResolve

back to summary

private Object readResolve()

Resolve singleton.

Returns:Object: the singleton instance, not null

resolveDate back to summary

resolveDate	back to summary
public EthiopicDate resolveDate(Map<TemporalField, Long> fieldValues, ResolverStyle resolverStyle) Overrides java.time.chrono.AbstractChronology.resolveDate. Implements java.time.chrono.Chronology.resolveDate. Doc from java.time.chrono.AbstractChronology.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 are resolved by this method, which may be overridden in subclasses. `EPOCH_DAY` - If present, this is converted to a date 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 last available era 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 date. In all three modes, the `YEAR` is validated. If the mode is smart or strict, then the month and day are validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the first month 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 date. 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 day of 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 date. 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 day of the first month 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 date. 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 date. 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 day of 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 date. 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. The default implementation is suitable for most calendar systems. If `java.time.temporal.ChronoField#YEAR_OF_ERA` is found without an `java.time.temporal.ChronoField#ERA` then the last era in `eras()` is used. The implementation assumes a 7 day week, that the first day-of-month has the value 1, that first day-of-year has the value 1, and that the first of the month and year always exists. 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:EthiopicDate the resolved date, null if insufficient information to create a date Annotations @Override

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

Overrides java.time.chrono.AbstractChronology.resolveDate.

Implements java.time.chrono.Chronology.resolveDate.

Doc from java.time.chrono.AbstractChronology.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 are resolved by this method, which may be overridden in subclasses.

EPOCH_DAY - If present, this is converted to a date 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 last available era 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 date. In all three modes, the YEAR is validated. If the mode is smart or strict, then the month and day are validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the first month 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 date. 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 day of 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 date. 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 day of the first month 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 date. 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 date. 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 day of 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 date. 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.

The default implementation is suitable for most calendar systems. If java.time.temporal.ChronoField#YEAR_OF_ERA is found without an java.time.temporal.ChronoField#ERA then the last era in eras() is used. The implementation assumes a 7 day week, that the first day-of-month has the value 1, that first day-of-year has the value 1, and that the first of the month and year always exists.

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:EthiopicDate

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

Annotations

@Override

zonedDateTime	back to summary
public ChronoZonedDateTime<EthiopicDate> zonedDateTime(TemporalAccessor temporal) Overrides default java.time.chrono.Chronology.zonedDateTime. Obtains a Ethiopic zoned date-time from another date-time object. Parameters temporal:TemporalAccessor the date-time object to convert, not null Returns:ChronoZonedDateTime<EthiopicDate> the Ethiopic zoned date-time, not null Annotations @Override @SuppressWarnings:unchecked Exceptions DateTimeException: if unable to create the date-time

zonedDateTime

back to summary

public ChronoZonedDateTime<EthiopicDate> zonedDateTime(TemporalAccessor temporal)

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

Obtains a Ethiopic zoned date-time from another date-time object.

Parameters

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

Returns:ChronoZonedDateTime<EthiopicDate>

the Ethiopic zoned date-time, not null

Annotations

@Override
@SuppressWarnings:unchecked

Exceptions

DateTimeException:: if unable to create the date-time

zonedDateTime back to summary

zonedDateTime	back to summary
public ChronoZonedDateTime<EthiopicDate> zonedDateTime(Instant instant, ZoneId zone) Overrides default java.time.chrono.Chronology.zonedDateTime. Obtains a Ethiopic zoned date-time in this chronology from an `Instant`. Parameters instant:Instant the instant to create the date-time from, not null zone:ZoneId the time-zone, not null Returns:ChronoZonedDateTime<EthiopicDate> the Ethiopic zoned date-time, not null Annotations @Override @SuppressWarnings:unchecked Exceptions DateTimeException: if the result exceeds the supported range