Examples of Chronology

com.facebook.presto.jdbc.internal.joda.time.Chronology
Chronology provides access to the individual date time fields for a chronological calendar system.
Various chronologies are supported by subclasses including ISO and GregorianJulian. To construct a Chronology you should use the factory methods on the chronology subclass in the chrono package.
For example, to obtain the current time in the coptic calendar system:
```
 DateTime dt = new DateTime(CopticChronology.getInstance()); 
```
The provided chronology implementations are:
- ISO - Based on the ISO8601 standard and suitable for use after about 1600
- GJ - Historically accurate calendar with Julian followed by Gregorian
- Gregorian - The Gregorian calendar system used for all time (proleptic)
- Julian - The Julian calendar system used for all time (proleptic)
- Buddhist - The Buddhist calendar system which is an offset in years from GJ
- Coptic - The Coptic calendar system which defines 30 day months
- Ethiopic - The Ethiopic calendar system which defines 30 day months
Hopefully future releases will contain more chronologies.
This class defines a number of fields with names from the ISO8601 standard. It does not 'strongly' define these fields however, thus implementations are free to interpret the field names as they wish. For example, a week could be defined as 10 days and a month as 40 days in a special WeirdChronology implementation. Clearly the GJ and ISO implementations provided use the field names as you would expect. @see com.facebook.presto.jdbc.internal.joda.time.chrono.ISOChronology @see com.facebook.presto.jdbc.internal.joda.time.chrono.GJChronology @see com.facebook.presto.jdbc.internal.joda.time.chrono.GregorianChronology @see com.facebook.presto.jdbc.internal.joda.time.chrono.JulianChronology @see com.facebook.presto.jdbc.internal.joda.time.chrono.CopticChronology @see com.facebook.presto.jdbc.internal.joda.time.chrono.BuddhistChronology @see com.facebook.presto.jdbc.internal.joda.time.chrono.EthiopicChronology @author Stephen Colebourne @author Brian S O'Neill @since 1.0
java.time.chrono.Chronology
A calendar system, used to organize and identify dates.
The main date and time API is built on the ISO calendar system. The chronology operates behind the scenes to represent the general concept of a calendar system. For example, the Japanese, Minguo, Thai Buddhist and others.
Most other calendar systems also operate on the shared concepts of year, month and day, linked to the cycles of the Earth around the Sun, and the Moon around the Earth. These shared concepts are defined by {@link ChronoField} and are availablefor use by any {@code Chronology} implementation:
```
 LocalDate isoDate = ... ThaiBuddhistDate thaiDate = ... int isoYear = isoDate.get(ChronoField.YEAR); int thaiYear = thaiDate.get(ChronoField.YEAR); 
```
As shown, although the date objects are in different calendar systems, represented by different {@code Chronology} instances, both can be queried using the same constant on {@code ChronoField}. For a full discussion of the implications of this, see {@link ChronoLocalDate}. In general, the advice is to use the known ISO-based {@code LocalDate}, rather than {@code ChronoLocalDate}.
While a {@code Chronology} object typically uses {@code ChronoField} and is based onan era, year-of-era, month-of-year, day-of-month model of a date, this is not required. A {@code Chronology} instance may represent a totally different kind of calendar system,such as the Mayan.
In practical terms, the {@code Chronology} instance also acts as a factory.The {@link #of(String)} method allows an instance to be looked up by identifier,while the {@link #ofLocale(Locale)} method allows lookup by locale.
The {@code Chronology} instance provides a set of methods to create {@code ChronoLocalDate} instances.The date classes are used to manipulate specific dates.
- {@link #dateNow() dateNow()}
- {@link #dateNow(Clock) dateNow(clock)}
- {@link #dateNow(ZoneId) dateNow(zone)}
- {@link #date(int,int,int) date(yearProleptic, month, day)}
- {@link #date(Era,int,int,int) date(era, yearOfEra, month, day)}
- {@link #dateYearDay(int,int) dateYearDay(yearProleptic, dayOfYear)}
- {@link #dateYearDay(Era,int,int) dateYearDay(era, yearOfEra, dayOfYear)}
- {@link #date(TemporalAccessor) date(TemporalAccessor)}
Adding New Calendars
The set of available chronologies can be extended by applications. Adding a new calendar system requires the writing of an implementation of {@code Chronology}, {@code ChronoLocalDate} and {@code Era}. The majority of the logic specific to the calendar system will be in {@code ChronoLocalDate}. The {@code Chronology} subclass acts as a factory.
To permit the discovery of additional chronologies, the {@link java.util.ServiceLoader ServiceLoader}is used. A file must be added to the {@code META-INF/services} directory with thename 'java.time.chrono.Chronology' listing the implementation classes. See the ServiceLoader for more details on service loading. For lookup by id or calendarType, the system provided calendars are found first followed by application provided calendars.
Each chronology must define a chronology ID that is unique within the system. If the chronology represents a calendar system defined by the CLDR specification then the calendar type is the concatenation of the CLDR type and, if applicable, the CLDR variant, @implSpec 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. Subclasses should be Serializable wherever possible. @since 1.8
org.elasticsearch.common.joda.time.Chronology
org.goda.time.Chronology
Chronology provides access to the individual date time fields for a chronological calendar system.
Various chronologies are supported by subclasses including ISO and GregorianJulian. To construct a Chronology you should use the factory methods on the chronology subclass in the chrono package.
For example, to obtain the current time in the coptic calendar system:
```
 DateTime dt = new DateTime(CopticChronology.getInstance()); 
```
The provided chronology implementations are:
- ISO - Based on the ISO8601 standard and suitable for use after about 1600
- GJ - Historically accurate calendar with Julian followed by Gregorian
- Gregorian - The Gregorian calendar system used for all time (proleptic)
- Julian - The Julian calendar system used for all time (proleptic)
- Buddhist - The Buddhist calendar system which is an offset in years from GJ
- Coptic - The Coptic calendar system which defines 30 day months
- Ethiopic - The Ethiopic calendar system which defines 30 day months
Hopefully future releases will contain more chronologies.
This class defines a number of fields with names from the ISO8601 standard. It does not 'strongly' define these fields however, thus implementations are free to interpret the field names as they wish. For example, a week could be defined as 10 days and a month as 40 days in a special WeirdChronology implementation. Clearly the GJ and ISO implementations provided use the field names as you would expect. @see org.joda.time.chrono.ISOChronology @see org.joda.time.chrono.GJChronology @see org.joda.time.chrono.GregorianChronology @see org.joda.time.chrono.JulianChronology @see org.joda.time.chrono.CopticChronology @see org.joda.time.chrono.BuddhistChronology @see org.joda.time.chrono.EthiopicChronology @author Stephen Colebourne @author Brian S O'Neill @since 1.0
org.joda.time.Chronology
Chronology provides access to the individual date time fields for a chronological calendar system.
Various chronologies are supported by subclasses including ISO and GregorianJulian. To construct a Chronology you should use the factory methods on the chronology subclass in the chrono package.
For example, to obtain the current time in the coptic calendar system:
```
 DateTime dt = new DateTime(CopticChronology.getInstance()); 
```
The provided chronology implementations are:
- ISO - Based on the ISO8601 standard and suitable for use after about 1600
- GJ - Historically accurate calendar with Julian followed by Gregorian
- Gregorian - The Gregorian calendar system used for all time (proleptic)
- Julian - The Julian calendar system used for all time (proleptic)
- Buddhist - The Buddhist calendar system which is an offset in years from GJ
- Coptic - The Coptic calendar system which defines 30 day months
- Ethiopic - The Ethiopic calendar system which defines 30 day months
Hopefully future releases will contain more chronologies.
This class defines a number of fields with names from the ISO8601 standard. It does not 'strongly' define these fields however, thus implementations are free to interpret the field names as they wish. For example, a week could be defined as 10 days and a month as 40 days in a special WeirdChronology implementation. Clearly the GJ and ISO implementations provided use the field names as you would expect. @see org.joda.time.chrono.ISOChronology @see org.joda.time.chrono.GJChronology @see org.joda.time.chrono.GregorianChronology @see org.joda.time.chrono.JulianChronology @see org.joda.time.chrono.CopticChronology @see org.joda.time.chrono.BuddhistChronology @see org.joda.time.chrono.EthiopicChronology @author Stephen Colebourne @author Brian S O'Neill @since 1.0
org.threeten.bp.chrono.Chronology
A calendar system, used to organize and identify dates.
The main date and time API is built on the ISO calendar system. This class operates behind the scenes to represent the general concept of a calendar system. For example, the Japanese, Minguo, Thai Buddhist and others.
Most other calendar systems also operate on the shared concepts of year, month and day, linked to the cycles of the Earth around the Sun, and the Moon around the Earth. These shared concepts are defined by {@link ChronoField} and are availalbefor use by any {@code Chronology} implementation:
```
 LocalDate isoDate = ... ChronoLocalDate<ThaiBuddhistChrono> minguoDate = ... int isoYear = isoDate.get(ChronoField.YEAR); int thaiYear = thaiDate.get(ChronoField.YEAR); 
```
As shown, although the date objects are in different calendar systems, represented by different {@code Chronology} instances, both can be queried using the same constant on {@code ChronoField}. For a full discussion of the implications of this, see {@link ChronoLocalDate}. In general, the advice is to use the known ISO-based {@code LocalDate}, rather than {@code ChronoLocalDate}.
While a {@code Chronology} object typically uses {@code ChronoField} and is based onan era, year-of-era, month-of-year, day-of-month model of a date, this is not required. A {@code Chronology} instance may represent a totally different kind of calendar system,such as the Mayan.
In practical terms, the {@code Chronology} instance also acts as a factory.The {@link #of(String)} method allows an instance to be looked up by identifier,while the {@link #ofLocale(Locale)} method allows lookup by locale.
The {@code Chronology} instance provides a set of methods to create {@code ChronoLocalDate} instances.The date classes are used to manipulate specific dates.
- {@link #dateNow() dateNow()}
- {@link #dateNow(Clock) dateNow(clock)}
- {@link #dateNow(ZoneId) dateNow(zone)}
- {@link #date(int,int,int) date(yearProleptic, month, day)}
- {@link #date(Era,int,int,int) date(era, yearOfEra, month, day)}
- {@link #dateYearDay(int,int) dateYearDay(yearProleptic, dayOfYear)}
- {@link #dateYearDay(Era,int,int) dateYearDay(era, yearOfEra, dayOfYear)}
- {@link #date(TemporalAccessor) date(TemporalAccessor)}
Adding New Calendars
The set of available chronologies can be extended by applications. Adding a new calendar system requires the writing of an implementation of {@code Chronology}, {@code ChronoLocalDate} and {@code Era}. The majority of the logic specific to the calendar system will be in {@code ChronoLocalDate}. The {@code Chronology} subclass acts as a factory.
To permit the discovery of additional chronologies, the {@link java.util.ServiceLoader ServiceLoader}is used. A file must be added to the {@code META-INF/services} directory with thename 'org.threeten.bp.chrono.Chrono' listing the implementation classes. See the ServiceLoader for more details on service loading. For lookup by id or calendarType, the system provided calendars are found first followed by application provided calendars.
Each chronology must define a chronology ID that is unique within the system. If the chronology represents a calendar system defined by the Unicode Locale Data Markup Language (LDML) specification then that calendar type should also be specified.
Specification for implementors
This class must be implemented with care to ensure other classes operate correctly. All implementations that can be instantiated must be final, immutable and thread-safe. Subclasses should be Serializable wherever possible.
In JDK 8, this is an interface with default methods. Since there are no default methods in JDK 7, an abstract class is used.

Examples of org.joda.time.Chronology

        assertEquals("2007-04-01T01:00:00.001-04:00", post.toString());
    }


    public void test_lenientChrononolgy_Chicago() {
        DateTimeZone zone = DateTimeZone.forID("America/Chicago");
        Chronology lenient = LenientChronology.getInstance(ISOChronology.getInstance(zone));
        DateTime dt = new DateTime(2007, 3, 11, 2, 30, 0, 0, lenient);
        assertEquals("2007-03-11T03:30:00.000-05:00", dt.toString());
    }

View Full Code Here

Examples of org.joda.time.Chronology

        DateTime dt = new DateTime(2007, 3, 11, 2, 30, 0, 0, lenient);
        assertEquals("2007-03-11T03:30:00.000-05:00", dt.toString());
    }


    public void test_lenientChrononolgy_Turk() {
        Chronology lenient = LenientChronology.getInstance(ISOChronology.getInstance(MOCK_TURK));
        DateTime dt = new DateTime(2007, 4, 1, 0, 30, 0, 0, lenient);
        assertEquals("2007-04-01T01:30:00.000-04:00", dt.toString());
    }

View Full Code Here

Examples of org.joda.time.Chronology

        assertEquals("2007-04-01T01:30:00.000-04:00", dt.toString());
    }


    public void test_strictChrononolgy_Chicago() {
        DateTimeZone zone = DateTimeZone.forID("America/Chicago");
        Chronology lenient = StrictChronology.getInstance(ISOChronology.getInstance(zone));
        try {
            new DateTime(2007, 3, 11, 2, 30, 0, 0, lenient);
            fail();
        } catch (IllegalArgumentException ex) {
            // expected

View Full Code Here

Examples of org.joda.time.Chronology

        }
    }


    public void test_isoChrononolgy_Chicago() {
        DateTimeZone zone = DateTimeZone.forID("America/Chicago");
        Chronology lenient = ISOChronology.getInstance(zone);
        try {
            new DateTime(2007, 3, 11, 2, 30, 0, 0, lenient);
            fail();
        } catch (IllegalArgumentException ex) {
            // expected

View Full Code Here

Examples of org.joda.time.Chronology

            // good
        }
    }


    public void testLeap_28feb() {
        Chronology chrono = GJChronology.getInstance();
        DateTime dt = new DateTime(2012, 2, 28, 0, 0, chrono);
        assertEquals(true, dt.year().isLeap());
        assertEquals(true, dt.monthOfYear().isLeap());
        assertEquals(false, dt.dayOfMonth().isLeap());
        assertEquals(false, dt.dayOfYear().isLeap());

View Full Code Here

Examples of org.joda.time.Chronology

        assertEquals(false, dt.dayOfMonth().isLeap());
        assertEquals(false, dt.dayOfYear().isLeap());
    }


    public void testLeap_29feb() {
        Chronology chrono = GJChronology.getInstance();
        DateTime dt = new DateTime(2012, 2, 29, 0, 0, chrono);
        assertEquals(true, dt.year().isLeap());
        assertEquals(true, dt.monthOfYear().isLeap());
        assertEquals(true, dt.dayOfMonth().isLeap());
        assertEquals(true, dt.dayOfYear().isLeap());

View Full Code Here

Examples of org.joda.time.Chronology

            assertEquals(dt.dayOfMonth().getMaximumValue(), ymd.dayOfMonth().getMaximumValue());
        }
    }


    public void testLeap_28feb() {
        Chronology chrono = ISOChronology.getInstance();
        DateTime dt = new DateTime(2012, 2, 28, 0, 0, chrono);
        assertEquals(true, dt.year().isLeap());
        assertEquals(true, dt.monthOfYear().isLeap());
        assertEquals(false, dt.dayOfMonth().isLeap());
        assertEquals(false, dt.dayOfYear().isLeap());

View Full Code Here

Examples of org.joda.time.Chronology

        assertEquals(false, dt.dayOfMonth().isLeap());
        assertEquals(false, dt.dayOfYear().isLeap());
    }


    public void testLeap_29feb() {
        Chronology chrono = ISOChronology.getInstance();
        DateTime dt = new DateTime(2012, 2, 29, 0, 0, chrono);
        assertEquals(true, dt.year().isLeap());
        assertEquals(true, dt.monthOfYear().isLeap());
        assertEquals(true, dt.dayOfMonth().isLeap());
        assertEquals(true, dt.dayOfYear().isLeap());

View Full Code Here

Examples of org.joda.time.Chronology

        assertEquals(dt13.getMillis(), fld.add(dt11.getMillis(), 2L));
        assertEquals(dt01.getMillis(), fld.add(dt11.getMillis(), 3L));
    }


    public void testLeap_5_13() {
        Chronology chrono = EthiopicChronology.getInstance();
        DateTime dt = new DateTime(3, 13, 5, 0, 0, chrono);
        assertEquals(true, dt.year().isLeap());
        assertEquals(true, dt.monthOfYear().isLeap());
        assertEquals(false, dt.dayOfMonth().isLeap());
        assertEquals(false, dt.dayOfYear().isLeap());

View Full Code Here

Examples of org.joda.time.Chronology

        assertEquals(false, dt.dayOfMonth().isLeap());
        assertEquals(false, dt.dayOfYear().isLeap());
    }


    public void testLeap_6_13() {
        Chronology chrono = EthiopicChronology.getInstance();
        DateTime dt = new DateTime(3, 13, 6, 0, 0, chrono);
        assertEquals(true, dt.year().isLeap());
        assertEquals(true, dt.monthOfYear().isLeap());
        assertEquals(true, dt.dayOfMonth().isLeap());
        assertEquals(true, dt.dayOfYear().isLeap());

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.

Examples of Chronology

Adding New Calendars

Specification for implementors

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology

Examples of org.joda.time.Chronology