public final class JapaneseChronology extends Chronology implements java.io.Serializable
This chronology defines the rules of the Japanese Imperial calendar system. This calendar system is primarily used in Japan. The Japanese Imperial calendar system is the same as the ISO calendar system apart from the era-based year numbering.
Japan introduced the Gregorian calendar starting with Meiji 6. Only Meiji and later eras are supported; dates before Meiji 6, January 1 are not supported.
The supported ChronoField instances are:
DAY_OF_WEEK
DAY_OF_MONTH
DAY_OF_YEAR
EPOCH_DAY
MONTH_OF_YEAR
PROLEPTIC_MONTH
YEAR_OF_ERA
YEAR
ERA
| Modifier and Type | Field and Description |
|---|---|
static JapaneseChronology |
INSTANCE
Singleton instance for Japanese chronology.
|
FROM| Modifier and Type | Method and Description |
|---|---|
JapaneseDate |
date(Era era,
int yearOfEra,
int month,
int dayOfMonth)
Obtains a local date in this chronology from the era, year-of-era,
month-of-year and day-of-month fields.
|
JapaneseDate |
date(int prolepticYear,
int month,
int dayOfMonth)
Obtains a local date in this chronology from the proleptic-year,
month-of-year and day-of-month fields.
|
JapaneseDate |
date(TemporalAccessor temporal)
Obtains a local date in this chronology from another temporal object.
|
JapaneseDate |
dateEpochDay(long epochDay)
Obtains a local date in this chronology from the epoch-day.
|
JapaneseDate |
dateNow()
Obtains the current local date in this chronology from the system clock in the default time-zone.
|
JapaneseDate |
dateNow(Clock clock)
Obtains the current local date in this chronology from the specified clock.
|
JapaneseDate |
dateNow(ZoneId zone)
Obtains the current local date in this chronology from the system clock in the specified time-zone.
|
JapaneseDate |
dateYearDay(Era era,
int yearOfEra,
int dayOfYear)
Obtains a local date in Japanese calendar system from the
era, year-of-era and day-of-year fields.
|
JapaneseDate |
dateYearDay(int prolepticYear,
int dayOfYear)
Obtains a local date in Japanese calendar system from the
proleptic-year and day-of-year fields.
|
JapaneseEra |
eraOf(int eraValue)
Returns the calendar system era object from the given numeric value.
|
java.util.List<Era> |
eras()
Gets the list of eras for the chronology.
|
java.lang.String |
getCalendarType()
Gets the calendar type of the underlying calendar system - 'japanese'.
|
java.lang.String |
getId()
Gets the ID of the chronology - 'Japanese'.
|
boolean |
isLeapYear(long prolepticYear)
Checks if the specified year is a leap year.
|
ChronoLocalDateTime<JapaneseDate> |
localDateTime(TemporalAccessor temporal)
Obtains a local date-time in this chronology from another temporal object.
|
int |
prolepticYear(Era era,
int yearOfEra)
Calculates the proleptic-year given the era and year-of-era.
|
ValueRange |
range(ChronoField field)
Gets the range of valid values for the specified field.
|
JapaneseDate |
resolveDate(java.util.Map<TemporalField,java.lang.Long> fieldValues,
ResolverStyle resolverStyle)
Resolves parsed
ChronoField values into a date during parsing. |
ChronoZonedDateTime<JapaneseDate> |
zonedDateTime(Instant instant,
ZoneId zone)
Obtains a zoned date-time in this chronology from an
Instant. |
ChronoZonedDateTime<JapaneseDate> |
zonedDateTime(TemporalAccessor temporal)
Obtains a zoned date-time in this chronology from another temporal object.
|
compareTo, equals, from, getAvailableChronologies, getDisplayName, hashCode, of, ofLocale, period, toStringpublic static final JapaneseChronology INSTANCE
public java.lang.String getId()
The ID uniquely identifies the Chronology.
It can be used to lookup the Chronology using Chronology.of(String).
getId in class ChronologygetCalendarType()public java.lang.String getCalendarType()
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'.
getCalendarType in class ChronologygetId()public JapaneseDate date(Era era, int yearOfEra, int month, int dayOfMonth)
Chronologydate in class Chronologyera - the era of the correct type for the chronology, not nullyearOfEra - the chronology year-of-eramonth - the chronology month-of-yeardayOfMonth - the chronology day-of-monthpublic JapaneseDate date(int prolepticYear, int month, int dayOfMonth)
Chronologydate in class ChronologyprolepticYear - the chronology proleptic-yearmonth - the chronology month-of-yeardayOfMonth - the chronology day-of-monthpublic JapaneseDate dateYearDay(Era era, int yearOfEra, int dayOfYear)
The day-of-year in this factory is expressed relative to the start of the year-of-era. This definition changes the normal meaning of day-of-year only in those years where the year-of-era is reset to one due to a change in the era. For example:
6th Jan Showa 64 = day-of-year 6 7th Jan Showa 64 = day-of-year 7 8th Jan Heisei 1 = day-of-year 1 9th Jan Heisei 1 = day-of-year 2
dateYearDay in class Chronologyera - the Japanese era, not nullyearOfEra - the year-of-eradayOfYear - the day-of-yearDateTimeException - if unable to create the datejava.lang.ClassCastException - if the era is not a JapaneseErapublic JapaneseDate dateYearDay(int prolepticYear, int dayOfYear)
The day-of-year in this factory is expressed relative to the start of the proleptic year. The Japanese proleptic year and day-of-year are the same as those in the ISO calendar system. They are not reset when the era changes.
dateYearDay in class ChronologyprolepticYear - the proleptic-yeardayOfYear - the day-of-yearDateTimeException - if unable to create the datepublic JapaneseDate dateEpochDay(long epochDay)
Chronology
The definition of EPOCH_DAY is the same
for all calendar systems, thus it can be used for conversion.
dateEpochDay in class ChronologyepochDay - the epoch daypublic JapaneseDate date(TemporalAccessor temporal)
Chronology
This creates a date in this chronology based on the specified TemporalAccessor.
The standard mechanism for conversion between date types is the
local epoch-day field.
date in class Chronologytemporal - the temporal object to convert, not nullpublic ChronoLocalDateTime<JapaneseDate> localDateTime(TemporalAccessor temporal)
Chronology
This creates a date-time in this chronology based on the specified TemporalAccessor.
The date of the date-time should be equivalent to that obtained by calling
Chronology.date(TemporalAccessor).
The standard mechanism for conversion between time types is the
nano-of-day field.
localDateTime in class Chronologytemporal - the temporal object to convert, not nullpublic ChronoZonedDateTime<JapaneseDate> zonedDateTime(TemporalAccessor temporal)
Chronology
This creates a date-time in this chronology based on the specified TemporalAccessor.
This should obtain a ZoneId using ZoneId.from(TemporalAccessor).
The date-time should be obtained by obtaining an Instant.
If that fails, the local date-time should be used.
zonedDateTime in class Chronologytemporal - the temporal object to convert, not nullpublic ChronoZonedDateTime<JapaneseDate> zonedDateTime(Instant instant, ZoneId zone)
ChronologyInstant.
This creates a zoned date-time with the same instant as that specified.
zonedDateTime in class Chronologyinstant - the instant to create the date-time from, not nullzone - the time-zone, not nullpublic JapaneseDate dateNow()
Chronology
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.
This implementation uses Chronology.dateNow(Clock).
dateNow in class Chronologypublic JapaneseDate dateNow(ZoneId zone)
Chronology
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.
dateNow in class Chronologyzone - the zone ID to use, not nullpublic JapaneseDate dateNow(Clock clock)
Chronology
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.
dateNow in class Chronologyclock - the clock to use, not nullpublic boolean isLeapYear(long prolepticYear)
Japanese calendar leap years occur exactly in line with ISO leap years. This method does not validate the year passed in, and only has a well-defined result for years in the supported range.
isLeapYear in class ChronologyprolepticYear - the proleptic-year to check, not validated for rangepublic int prolepticYear(Era era, int yearOfEra)
ChronologyThis combines the era and year-of-era into the single proleptic-year field.
prolepticYear in class Chronologyera - the era of the correct type for the chronology, not nullyearOfEra - the chronology year-of-erapublic JapaneseEra eraOf(int eraValue)
JapaneseEra.HEISEI, JapaneseEra.SHOWA,JapaneseEra.TAISHO,
JapaneseEra.MEIJI), only Meiji and later eras are supported.eraOf in class ChronologyeraValue - the era valueEra for the given numeric era valueDateTimeException - if eraValue is invalidpublic java.util.List<Era> eras()
ChronologyMost 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.
eras in class Chronologypublic ValueRange range(ChronoField field)
Chronology
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.
range in class Chronologyfield - the field to get the range for, not nullpublic JapaneseDate resolveDate(java.util.Map<TemporalField,java.lang.Long> fieldValues, ResolverStyle resolverStyle)
ChronologyChronoField 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.
The default implementation, which explains typical resolve behaviour,
is provided in AbstractChronology.
resolveDate in class ChronologyfieldValues - the map of fields to values, which can be updated, not nullresolverStyle - the requested type of resolve, not nullCopyright © 2014. All Rights Reserved.