pack-priv final Class ChronoLocalDateTimeImpl<D extends ChronoLocalDate>

Implements java.time.chrono.ChronoLocalDateTime.atZone.

Doc from java.time.chrono.ChronoLocalDateTime.atZone.

Combines this time with a time-zone to create a ChronoZonedDateTime.

This returns a ChronoZonedDateTime formed from this date-time at the specified time-zone. The result will match this date-time as closely as possible. Time-zone rules, such as daylight savings, mean that not every local date-time is valid for the specified zone, thus the local date-time may be adjusted.

The local date-time is resolved to a single instant on the time-line. This is achieved by finding a valid offset from UTC/Greenwich for the local date-time as defined by the rules of the zone ID.

In most cases, there is only one valid offset for a local date-time. In the case of an overlap, where clocks are set back, there are two valid offsets. This method uses the earlier offset typically corresponding to "summer".

In the case of a gap, where clocks jump forward, there is no valid offset. Instead, the local date-time is adjusted to be later by the length of the gap. For a typical one hour daylight savings change, the local date-time will be moved one hour later into the offset typically corresponding to "summer".

To obtain the later offset during an overlap, call ChronoZonedDateTime#withLaterOffsetAtOverlap() on the result of this method.

Annotations

@Override

Overrides java.lang.Object.equals.

Implements java.time.chrono.ChronoLocalDateTime.equals.

Doc from java.time.chrono.ChronoLocalDateTime.equals.

Checks if this date-time is equal to another date-time, including the chronology.

Compares this date-time with another ensuring that the date-time and chronology are the same.

Annotations

@Override

Overrides default java.time.temporal.TemporalAccessor.get.

Doc from java.time.temporal.TemporalAccessor.get.

Gets the value of the specified field as an int.

This queries the date-time for the value of the specified field. The returned value will always be within the valid range of values for the field. If the date-time cannot return the value, because the field is unsupported or for some other reason, an exception will be thrown.

Annotations

@Override

Implements java.time.temporal.TemporalAccessor.getLong.

Doc from java.time.temporal.TemporalAccessor.getLong.

Gets the value of the specified field as a long.

This queries the date-time for the value of the specified field. The returned value may be outside the valid range of values for the field. If the date-time cannot return the value, because the field is unsupported or for some other reason, an exception will be thrown.

Annotations

@Override

Overrides java.lang.Object.hashCode.

Implements java.time.chrono.ChronoLocalDateTime.hashCode.

Doc from java.time.chrono.ChronoLocalDateTime.hashCode.

A hash code for this date-time.

Annotations

@Override

Implements java.time.chrono.ChronoLocalDateTime.isSupported, java.time.temporal.TemporalAccessor.isSupported.

Doc from java.time.chrono.ChronoLocalDateTime.isSupported.

Checks if the specified field is supported.

This checks if the specified field can be queried on this date-time. If false, then calling the range, get and with(TemporalField, long) methods will throw an exception.

The set of supported fields is defined by the chronology and normally includes all ChronoField date and time fields.

If the field is not a ChronoField, then the result of this method is obtained by invoking TemporalField.isSupportedBy(TemporalAccessor) passing this as the argument. Whether the field is supported is determined by the field.

Annotations

@Override

Implements java.time.chrono.ChronoLocalDateTime.plus, java.time.temporal.Temporal.plus.

Doc from java.time.chrono.ChronoLocalDateTime.plus.

Returns an object of the same type as this object with the specified period added.

This method returns a new object based on this one with the specified period added. For example, on a LocalDate, this could be used to add a number of years, months or days. The returned object will have the same observable type as this 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 adding one month would be unclear. In cases like this, the field 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.

Annotations

@Override

Overrides default java.time.temporal.TemporalAccessor.range.

Doc from java.time.temporal.TemporalAccessor.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. The value of this temporal object is used to enhance the accuracy of the returned range. If the date-time cannot return the range, because the field is unsupported or for some other reason, an exception will be thrown.

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.

Annotations

@Override

Implements java.time.chrono.ChronoLocalDateTime.toLocalDate.

Doc from java.time.chrono.ChronoLocalDateTime.toLocalDate.

Gets the local date part of this date-time.

This returns a local date with the same year, month and day as this date-time.

Annotations

@Override

Implements java.time.chrono.ChronoLocalDateTime.toLocalTime.

Doc from java.time.chrono.ChronoLocalDateTime.toLocalTime.

Gets the local time part of this date-time.

This returns a local time with the same hour, minute, second and nanosecond as this date-time.

Annotations

@Override

Overrides java.lang.Object.toString.

Implements java.time.chrono.ChronoLocalDateTime.toString.

Doc from java.time.chrono.ChronoLocalDateTime.toString.

Outputs this date-time as a String.

The output will include the full local date-time.

Annotations

@Override

Implements java.time.temporal.Temporal.until.

Doc from java.time.temporal.Temporal.until.

Calculates the amount of time until another temporal in terms of the specified unit.

This calculates the amount of time between two temporal objects in terms of a single TemporalUnit. The start and end points are this and the specified temporal. The end point is converted to be of the same type as the start point if different. The result will be negative if the end is before the start. For example, the amount in hours between two temporal objects can be calculated using startTime.until(endTime, HOURS).

The calculation returns a whole number, representing the number of complete units between the two temporals. For example, the amount in hours between the times 11:30 and 13:29 will only be one hour as it is one minute short of two hours.

There are two equivalent ways of using this method. The first is to invoke this method directly. The second is to use TemporalUnit#between(Temporal, Temporal):

  // these two lines are equivalent
  amount = start.until(end, unit);
  amount = unit.between(start, end);

For example, this method allows the number of days between two dates to be calculated:

 long daysBetween = start.until(end, DAYS);
 // or alternatively
 long daysBetween = DAYS.between(start, end);

Annotations

@Override

Overrides default java.time.chrono.ChronoLocalDateTime.with, java.time.temporal.Temporal.with.

Doc from java.time.chrono.ChronoLocalDateTime.with.

Returns an adjusted object of the same type as this object with the adjustment made.

This adjusts this date-time according to the rules of the specified adjuster. A simple adjuster might simply set the one of the fields, such as the year field. A more complex adjuster might set the date to the last day of the month. A selection of common adjustments is provided in TemporalAdjusters. These include finding the "last day of the month" and "next Wednesday". The adjuster is responsible for handling special cases, such as the varying lengths of month and leap years.

Some example code indicating how and why this method is used:

 date = date.with(Month.JULY);        // most key classes implement TemporalAdjuster
 date = date.with(lastDayOfMonth());  // static import from Adjusters
 date = date.with(next(WEDNESDAY));   // static import from Adjusters and DayOfWeek

Annotations

@Override

Implements java.time.chrono.ChronoLocalDateTime.with, java.time.temporal.Temporal.with.

Doc from java.time.chrono.ChronoLocalDateTime.with.

Returns an object of the same type as this object with the specified field altered.

This returns a new object based on this one with the value for the specified field changed. For example, on a LocalDate, this could be used to set the year, month or day-of-month. The returned object will have the same observable type as this 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 field 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.

Annotations

@Override