* This counts the second within the minute, from 0 to 59. * This field has the same meaning for all calendar systems. */ SECOND_OF_MINUTE("SecondOfMinute", 0, 59), /** * The second-of-day. *
* This counts the second within the day, from 0 to (24 * 60 * 60) - 1. * This field has the same meaning for all calendar systems. */ SECOND_OF_DAY("SecondOfDay", 0, 86400 - 1), /** * The minute-of-hour. *
* This counts the minute within the hour, from 0 to 59. * This field has the same meaning for all calendar systems. */ MINUTE_OF_HOUR("MinuteOfHour", 0, 59), /** * The hour-of-day. *
* This counts the hour within the day, from 0 to 23. * This is the hour that would be observed on a standard 24-hour digital clock. * This field has the same meaning for all calendar systems. */ HOUR_OF_DAY("HourOfDay", 0, 23), /** * The day-of-month. *
* This represents the concept of the day within the month. * In the default ISO calendar system, this has values from 1 to 31 in most months. * April, June, September, November have days from 1 to 30, while February has days * from 1 to 28, or 29 in a leap year. *
* Non-ISO calendar systems should implement this field using the most recognized * day-of-month values for users of the calendar system. * Normally, this is a count of days from 1 to the length of the month. */ DAY_OF_MONTH("DayOfMonth", 1, 31), /** * The month-of-year, such as March. *
* This represents the concept of the month within the year. * In the default ISO calendar system, this has values from January (1) to December (12). *
* Non-ISO calendar systems should implement this field using the most recognized * month-of-year values for users of the calendar system. * Normally, this is a count of months starting from 1. */ MONTH_OF_YEAR("MonthOfYear", 1, 12), /** * The proleptic year, such as 2012. *
* This represents the concept of the year, counting sequentially and using negative numbers. * The proleptic year is not interpreted in terms of the era. * See {@link #YEAR_OF_ERA} for an example showing the mapping from proleptic year to year-of-era. *
* The standard mental model for a date is based on three concepts - year, month and day. * These map onto the {@code YEAR}, {@code MONTH_OF_YEAR} and {@code DAY_OF_MONTH} fields. * Note that there is no reference to eras. * The full model for a date requires four concepts - era, year, month and day. These map onto * the {@code ERA}, {@code YEAR_OF_ERA}, {@code MONTH_OF_YEAR} and {@code DAY_OF_MONTH} fields. * Whether this field or {@code YEAR_OF_ERA} is used depends on which mental model is being used. * See {@link ChronoLocalDate} for more discussion on this topic. *
* Non-ISO calendar systems should implement this field as follows. * If the calendar system has only two eras, before and after a fixed date, then the * proleptic-year value must be the same as the year-of-era value for the later era, * and increasingly negative for the earlier era. * If the calendar system has more than two eras, then the proleptic-year value may be * defined with any appropriate value, although defining it to be the same as ISO may be * the best option. */ YEAR("Year", -999_999_999, 999_999_999); private final String name; private final int min; private final int max; private ChronoField(String name, int min, int max) { this.name = name; this.min= min; this.max= max; } /** * Checks that the specified value is valid for this field. *
* * @param value the value to check * @return the value that was passed in */ public int checkValidValue(int value) { if (value >= min && value <= max) { return value; } throw new DateTimeException("Invalid value for " + name + " value: " + value); } public String toString() { return name; } }