This class uses a Chronology internally. The Chronology determines how the millisecond instant value is converted into the date time fields. The default Chronology is ISOChronology
which is the agreed international standard and compatible with the modern Gregorian calendar.
Each individual field can be accessed in two ways:
getHourOfDay()
hourOfDay().get()
MutableDateTime is mutable and not thread-safe, unless concurrent threads are not invoking mutator methods. @author Guy Allard @author Brian S O'Neill @author Stephen Colebourne @author Mike Schrag @since 1.0 @see DateTime
This class uses a Chronology internally. The Chronology determines how the millisecond instant value is converted into the date time fields. The default Chronology is ISOChronology
which is the agreed international standard and compatable with the modern Gregorian calendar.
Each individual field can be accessed in two ways:
getHourOfDay()
hourOfDay().get()
MutableDateTime is mutable and not thread-safe, unless concurrent threads are not invoking mutator methods. @author Guy Allard @author Brian S O'Neill @author Stephen Colebourne @author Mike Schrag @since 1.0 @see DateTime
This class uses a Chronology internally. The Chronology determines how the millisecond instant value is converted into the date time fields. The default Chronology is ISOChronology
which is the agreed international standard and compatable with the modern Gregorian calendar.
Each individual field can be accessed in two ways:
getHourOfDay()
hourOfDay().get()
MutableDateTime is mutable and not thread-safe, unless concurrent threads are not invoking mutator methods. @author Guy Allard @author Brian S O'Neill @author Stephen Colebourne @author Mike Schrag @since 1.0 @see DateTime
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|