TemporalField
Related Doc:
package temporal
Returns a copy of the specified temporal object with the value of this field set.
Returns a copy of the specified temporal object with the value of this field set.
This returns a new temporal object based on the specified one with the value for
this field changed. For example, on a LocalDate, this could be used to
set the year, month or day-of-month.
The returned object has the same observable type as the specified object.
In some cases, changing a field is not fully defined. For example, if the target object is a date representing the 31st January, then changing the month to February would be unclear. In cases like this, the implementation is responsible for resolving the result. Typically it will choose the previous valid date, which would be the last valid day of February in this example.
There are two equivalent ways of using this method.
The first is to invoke this method directly.
The second is to use long):
// these two lines are equivalent, but the second approach is recommended temporal = thisField.adjustInto(temporal); temporal = temporal.with(thisField);It is recommended to use the second approach,
with(TemporalField),
as it is a lot clearer to read in code.Implementations should perform any queries or calculations using the fields
available in ChronoField.
If the field is not supported a DateTimeException must be thrown.
Implementations must not alter the specified temporal object. Instead, an adjusted copy of the original must be returned. This provides equivalent, safe behavior for immutable and mutable implementations.
the type of the Temporal object
the temporal object to adjust, not null
the new value of the field
the adjusted temporal object, not null
DateTimeException if the field cannot be set
Gets the unit that the field is measured in.
Gets the unit that the field is measured in.
The unit of the field is the period that varies within the range.
For example, in the field 'MonthOfYear', the unit is 'Months'.
See also #getRangeUnit().
the period unit defining the base unit of the field, not null
Gets the display name for the field in the requested locale.
Gets the display name for the field in the requested locale.
If there is no display name for the locale then a suitable default must be returned.
The default implementation must check the locale is not null
and return toString().
the locale to use, not null
the display name for the locale or a suitable default, not null
Gets the value of this field from the specified temporal object.
Gets the value of this field from the specified temporal object.
This queries the temporal object for the value of this field.
There are two equivalent ways of using this method.
The first is to invoke this method directly.
The second is to use TemporalAccessor#getLong(TemporalField)
(or TemporalAccessor#get(TemporalField)):
// these two lines are equivalent, but the second approach is recommended temporal = thisField.getFrom(temporal); temporal = temporal.getLong(thisField);It is recommended to use the second approach,
getLong(TemporalField),
as it is a lot clearer to read in code.Implementations should perform any queries or calculations using the fields
available in ChronoField.
If the field is not supported a DateTimeException must be thrown.
the temporal object to query, not null
the value of this field, not null
DateTimeException if a value for the field cannot be obtained
Gets the range that the field is bound by.
Gets the range that the field is bound by.
The range of the field is the period that the field varies within.
For example, in the field 'MonthOfYear', the range is 'Years'.
See also #getBaseUnit().
The range is never null. For example, the 'Year' field is shorthand for 'YearOfForever'. It therefore has a unit of 'Years' and a range of 'Forever'.
the period unit defining the range of the field, not null
Checks if this field is date-based.
Checks if this field is date-based.
A date-based field can be derived from epoch-day
true if date-based
Checks if this field is supported by the temporal object.
Checks if this field is supported by the temporal object.
This determines whether the temporal accessor supports this field. If this returns false, the the temporal cannot be queried for this field.
There are two equivalent ways of using this method.
The first is to invoke this method directly.
The second is to use TemporalAccessor#isSupported(TemporalField):
// these two lines are equivalent, but the second approach is recommended temporal = thisField.isSupportedBy(temporal); temporal = temporal.isSupported(thisField);It is recommended to use the second approach,
isSupported(TemporalField),
as it is a lot clearer to read in code.Implementations should determine whether they are supported using the fields
available in ChronoField.
the temporal object to query, not null
true if the date-time can be queried for this field, false if not
Checks if this field is time-based.
Checks if this field is time-based.
A time-based field can be derived from nano-of-day
true if time-based
Gets the range of valid values for the field.
Gets the range of valid values for the field.
All fields can be expressed as a long integer.
This method returns an object that describes the valid range for that value.
This method is generally only applicable to the ISO-8601 calendar system.
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.
the range of valid values for the field, not null
Get the range of valid values for this field using the temporal object to refine the result.
Get the range of valid values for this field using the temporal object to refine the result.
This uses the temporal object to find the range of valid values for the field.
This is similar to #range(), however this method refines the result
using the temporal. For example, if the field is DAY_OF_MONTH the
range method is not accurate as there are four possible month lengths,
28, 29, 30 and 31 days. Using this method with a date allows the range to be
accurate, returning just one of those four options.
There are two equivalent ways of using this method.
The first is to invoke this method directly.
The second is to use TemporalAccessor#range(TemporalField):
// these two lines are equivalent, but the second approach is recommended temporal = thisField.rangeRefinedBy(temporal); temporal = temporal.range(thisField);It is recommended to use the second approach,
range(TemporalField),
as it is a lot clearer to read in code.Implementations should perform any queries or calculations using the fields
available in ChronoField.
If the field is not supported a DateTimeException must be thrown.
the temporal object used to refine the result, not null
the range of valid values for this field, not null
DateTimeException if the range for the field cannot be obtained
Resolves the date/time information in the builder
Resolves the date/time information in the builder
This method is invoked during the resolve of the builder.
Implementations should combine the associated field with others to form
objects like LocalDate, LocalTime and LocalDateTime
the map of fields to values, which can be updated, not null
the partially complete temporal to query for zone and chronology; querying for other things is undefined and not recommended, not null
the requested type of resolve, not null
the resolved temporal object; null if resolving only changed the map, or no resolve occurred
ArithmeticException if numeric overflow occurs
DateTimeException if resolving results in an error. This must not be thrown
by querying a field on the temporal without first checking if it is supported
A field of date-time, such as month-of-year or hour-of-minute.
Date and time is expressed using fields which partition the time-line into something meaningful for humans. Implementations of this interface represent those fields.
The most commonly used units are defined in
ChronoField. Further fields are supplied inIsoFields,WeekFieldsandJulianFields. Fields can also be written by application code by implementing this interface.The field works using double dispatch. Client code calls methods on a date-time like
LocalDateTimewhich check if the field is aChronoField. If it is, then the date-time must handle it. Otherwise, the method call is re-dispatched to the matching method in this interface.Specification for implementors
This interface must be implemented with care to ensure other classes operate correctly. All implementations that can be instantiated must be final, immutable and thread-safe. Implementations should be
Serializablewhere possible. An enum is as effective implementation choice.