Examples of Calendar

  • gov.nysenate.openleg.model.Calendar
    @author Graylin Kim
  • java.util.Calendar
    The Calendar class is an abstract class that provides methods for converting between a specific instant in time and a set of {@link #fields calendar fields} such as YEAR, MONTH,DAY_OF_MONTH, HOUR, and so on, and for manipulating the calendar fields, such as getting the date of the next week. An instant in time can be represented by a millisecond value that is an offset from the Epoch, January 1, 1970 00:00:00.000 GMT (Gregorian).

    The class also provides additional fields and methods for implementing a concrete calendar system outside the package. Those fields and methods are defined as protected.

    Like other locale-sensitive classes, Calendar provides a class method, getInstance, for getting a generally useful object of this type. Calendar's getInstance method returns a Calendar object whose calendar fields have been initialized with the current date and time:

     Calendar rightNow = Calendar.getInstance(); 

    A Calendar object can produce all the calendar field values needed to implement the date-time formatting for a particular language and calendar style (for example, Japanese-Gregorian, Japanese-Traditional). Calendar defines the range of values returned by certain calendar fields, as well as their meaning. For example, the first month of the calendar system has value MONTH == JANUARY for all calendars. Other values are defined by the concrete subclass, such as ERA. See individual field documentation and subclass documentation for details.

    Getting and Setting Calendar Field Values

    The calendar field values can be set by calling the set methods. Any field values set in a Calendar will not be interpreted until it needs to calculate its time value (milliseconds from the Epoch) or values of the calendar fields. Calling the get, getTimeInMillis, getTime, add and roll involves such calculation.


    Calendar has two modes for interpreting the calendar fields, lenient and non-lenient. When a Calendar is in lenient mode, it accepts a wider range of calendar field values than it produces. When a Calendar recomputes calendar field values for return by get(), all of the calendar fields are normalized. For example, a lenient GregorianCalendar interprets MONTH == JANUARY, DAY_OF_MONTH == 32 as February 1.

    When a Calendar is in non-lenient mode, it throws an exception if there is any inconsistency in its calendar fields. For example, a GregorianCalendar always produces DAY_OF_MONTH values between 1 and the length of the month. A non-lenient GregorianCalendar throws an exception upon calculating its time or calendar field values if any out-of-range field value has been set.

    First Week

    Calendar defines a locale-specific seven day week using two parameters: the first day of the week and the minimal days in first week (from 1 to 7). These numbers are taken from the locale resource data when a Calendar is constructed. They may also be specified explicitly through the methods for setting their values.

    When setting or getting the WEEK_OF_MONTH or WEEK_OF_YEAR fields, Calendar must determine the first week of the month or year as a reference point. The first week of a month or year is defined as the earliest seven day period beginning on getFirstDayOfWeek() and containing at least getMinimalDaysInFirstWeek() days of that month or year. Weeks numbered ..., -1, 0 precede the first week; weeks numbered 2, 3,... follow it. Note that the normalized numbering returned by get() may be different. For example, a specific Calendar subclass may designate the week before week 1 of a year as week n of the previous year.

    Calendar Fields Resolution

    When computing a date and time from the calendar fields, there may be insufficient information for the computation (such as only year and month with no day of month), or there may be inconsistent information (such as Tuesday, July 15, 1996 (Gregorian) -- July 15, 1996 is actually a Monday). Calendar will resolve calendar field values to determine the date and time in the following way.

    If there is any conflict in calendar field values, Calendar gives priorities to calendar fields that have been set more recently. The following are the default combinations of the calendar fields. The most recent combination, as determined by the most recently set single field, will be used.

    For the date fields:

    For the time of day fields:

    If there are any calendar fields whose values haven't been set in the selected field combination, Calendar uses their default values. The default value of each field may vary by concrete calendar systems. For example, in GregorianCalendar, the default of a field is the same as that of the start of the Epoch: i.e., YEAR = 1970, MONTH = JANUARY, DAY_OF_MONTH = 1, etc.

    Note: There are certain possible ambiguities in interpretation of certain singular times, which are resolved in the following ways:

    1. 23:59 is the last minute of the day and 00:00 is the first minute of the next day. Thus, 23:59 on Dec 31, 1999 < 00:00 on Jan 1, 2000 < 00:01 on Jan 1, 2000.
    2. Although historically not precise, midnight also belongs to "am", and noon belongs to "pm", so on the same day, 12:00 am (midnight) < 12:01 am, and 12:00 pm (noon) < 12:01 pm

    The date or time format strings are not part of the definition of a calendar, as those must be modifiable or overridable by the user at runtime. Use {@link DateFormat}to format dates.

    Field Manipulation

    The calendar fields can be changed using three methods: set(), add(), and roll().

    set(f, value) changes calendar field f to value. In addition, it sets an internal member variable to indicate that calendar field f has been changed. Although calendar field f is changed immediately, the calendar's time value in milliseconds is not recomputed until the next call to get(), getTime(), getTimeInMillis(), add(), or roll() is made. Thus, multiple calls to set() do not trigger multiple, unnecessary computations. As a result of changing a calendar field using set(), other calendar fields may also change, depending on the calendar field, the calendar field value, and the calendar system. In addition, get(f) will not necessarily return value set by the call to the set method after the calendar fields have been recomputed. The specifics are determined by the concrete calendar class.

    Example: Consider a GregorianCalendar originally set to August 31, 1999. Calling set(Calendar.MONTH, Calendar.SEPTEMBER) sets the date to September 31, 1999. This is a temporary internal representation that resolves to October 1, 1999 if getTime()is then called. However, a call to set(Calendar.DAY_OF_MONTH, 30) before the call to getTime() sets the date to September 30, 1999, since no recomputation occurs after set() itself.

    add(f, delta) adds delta to field f. This is equivalent to calling set(f, get(f) + delta) with two adjustments:

    Add rule 1. The value of field f after the call minus the value of field f before the call is delta, modulo any overflow that has occurred in field f. Overflow occurs when a field value exceeds its range and, as a result, the next larger field is incremented or decremented and the field value is adjusted back into its range.

    Add rule 2. If a smaller field is expected to be invariant, but it is impossible for it to be equal to its prior value because of changes in its minimum or maximum after field f is changed or other constraints, such as time zone offset changes, then its value is adjusted to be as close as possible to its expected value. A smaller field represents a smaller unit of time. HOUR is a smaller field than DAY_OF_MONTH. No adjustment is made to smaller fields that are not expected to be invariant. The calendar system determines what fields are expected to be invariant.

    In addition, unlike set(), add() forces an immediate recomputation of the calendar's milliseconds and all fields.

    Example: Consider a GregorianCalendar originally set to August 31, 1999. Calling add(Calendar.MONTH, 13) sets the calendar to September 30, 2000. Add rule 1 sets the MONTH field to September, since adding 13 months to August gives September of the next year. Since DAY_OF_MONTH cannot be 31 in September in a GregorianCalendar, add rule 2 sets the DAY_OF_MONTH to 30, the closest possible value. Although it is a smaller field, DAY_OF_WEEK is not adjusted by rule 2, since it is expected to change when the month changes in a GregorianCalendar.

    roll(f, delta) adds delta to field f without changing larger fields. This is equivalent to calling add(f, delta) with the following adjustment:

    Roll rule. Larger fields are unchanged after the call. A larger field represents a larger unit of time. DAY_OF_MONTH is a larger field than HOUR.

    Example: See {@link java.util.GregorianCalendar#roll(int,int)}.

    Usage model. To motivate the behavior of add() and roll(), consider a user interface component with increment and decrement buttons for the month, day, and year, and an underlying GregorianCalendar. If the interface reads January 31, 1999 and the user presses the month increment button, what should it read? If the underlying implementation uses set(), it might read March 3, 1999. A better result would be February 28, 1999. Furthermore, if the user presses the month increment button again, it should read March 31, 1999, not March 28, 1999. By saving the original date and using either add() or roll(), depending on whether larger fields should be affected, the user interface can behave as most users will intuitively expect.

    @see java.lang.System#currentTimeMillis() @see Date @see GregorianCalendar @see TimeZone @see java.text.DateFormat @version 1.89, 08/21/08 @author Mark Davis, David Goldsmith, Chen-Lieh Huang, Alan Liu @since JDK1.1
  • net.fortuna.ical4j.model.Calendar
  • net.lalotech.struts2.map.components.Calendar
    @author Windows7x64
  • oauth.common.Calendar
  • oauth2.common.Calendar
  • org.apache.pivot.wtk.Calendar
    Component that allows the user to select a date.
  • org.drools.time.Calendar
  • org.japura.gui.calendar.Calendar

    Copyright (C) 2011-2013 Carlos Eduardo Leite de Andrade

    This library is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

    This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public License along with this program. If not, see www.gnu.org/licenses/

    For more information, contact: www.japura.org

    @author Carlos Eduardo Leite de Andrade

  • org.jquantlib.time.Calendar
    This class provides methods for determining whether a date is a business day or a holiday for a given market, and for incrementing/decrementing a date of a given number of business days.

    A calendar should be defined for specific exchange holiday schedule or for general country holiday schedule. Legacy city holiday schedule calendars will be moved to the exchange/country convention. @author Richard Gomes

  • org.kie.api.time.Calendar
  • org.mifosplatform.portfolio.calendar.domain.Calendar
  • org.openfaces.component.calendar.Calendar
    The Calendar component enables the user to select a date from a one-month calendar and easily navigate between months and years. A specific group of dates can be included in a date range. The Calendar component can use the client's locale or a specified one. Various style options for different parts of the Calendar component let you create the desired look-and-feel. @author Kharchenko
  • org.openfeed.proto.inst.Calendar
  • org.primefaces.component.calendar.Calendar
  • org.quartz.Calendar

    An interface to be implemented by objects that define spaces of time during which an associated {@link Trigger} may fire. Calendars do not define actual fire times, but rather are used to limit a Trigger from firing on its normal schedule if necessary. Most Calendars include all times by default and allow the user to specify times to exclude. As such, it is often useful to think of Calendars as being used to exclude a block of time — as opposed to include a block of time. (i.e. the schedule "fire every five minutes except on Sundays" could be implemented with a SimpleTrigger and a WeeklyCalendar which excludes Sundays)

    Implementations MUST take care of being properly Cloneable and Serializable.

    @author James House @author Juergen Donnerstag
  • org.sgx.yuigwt.yui.widget.calendar.Calendar
    ary.com/yui/docs/api/classes/Calendar.htm @see http://yuilibrary.com/yui/docs/api/classes/CalendarBase.htm @author sg
  • org.wicketstuff.yui.markup.html.calendar.Calendar
    Calendar component based on the Calendar of Yahoo UI Library. @author Eelco Hillenius
  • org.zkoss.zul.Calendar
    A calendar.

    Default {@link #getZclass}: z-calendar. (since 3.5.0) @author tomyeh

  • org.zkoss.zul.api.Calendar
    A calendar.

    Default {@link #getZclass}: z-calendar. (since 3.5.0) @author tomyeh @since 3.5.2

  • pivot.wtk.Calendar
    Component that allows the user to select a date. @author tvolkert @author gbrown

  • Examples of com.excilys.ebi.bank.model.Calendar


      public Calendar getCalendar(Integer year, Integer month) {

        Calendar calendar = new Calendar();

        // build months
        List<DateTime> months = calendar.getMonths();

        DateMidnight thisMonth = getDefaultDateTime().toDateMidnight().withDayOfMonth(1);

        // display last 6 months
        while (months.size() < 6) {
          thisMonth = thisMonth.minusMonths(1);


        // build selectedMonth
        if (year != null) {
          notNull(month, "month is required if year is specified");
          DateTime selectedMonth = new DateMidnight().withDayOfMonth(1).withYear(year).withMonthOfYear(month).toDateTime();

        return calendar;
    View Full Code Here

    Examples of com.google.api.services.calendar.Calendar

            bodyTrackHelper.setDefaultStyle(apiKey.getGuestId(), "google_calendar", "events", channelStyle);

        private void loadHistory(UpdateInfo updateInfo, boolean incremental) throws Exception {
            Calendar calendar = getCalendar(updateInfo.apiKey);
            String pageToken = null;
            long apiKeyId = updateInfo.apiKey.getId();
            List<String> existingCalendarIds = getExistingCalendarIds(apiKeyId);
            List<CalendarListEntry> remoteCalendars = new ArrayList<CalendarListEntry>();
            List<CalendarConfig> configs = new ArrayList<CalendarConfig>();
            do {
                final long then = System.currentTimeMillis();
                final Calendar.CalendarList.List list = calendar.calendarList().list().setPageToken(pageToken);
                final String query = list.getUriTemplate();
                CalendarList calendarList = null;
                try {
                    calendarList = list.execute();
                    countSuccessfulApiCall(updateInfo.apiKey, updateInfo.objectTypes, then, query);
    View Full Code Here

    Examples of com.google.api.services.calendar.model.Calendar

              System.out.println("Error Message: " + e.getMessage());

          // Create 2 Calendar Entries to insert.
          Calendar entry1 = new Calendar().setSummary("Calendar for Testing 1");
          client.calendars().insert(entry1).queue(batch, callback);

          Calendar entry2 = new Calendar().setSummary("Calendar for Testing 2");
          client.calendars().insert(entry2).queue(batch, callback);

    View Full Code Here

    Examples of com.googlecode.wicket.jquery.ui.calendar.Calendar

        options.set("monthNames", monthes.toString());
        options.set("monthNamesShort", shortMonthes.toString());
        options.set("dayNames", days.toString());
        options.set("dayNamesShort", shortDays.toString());
        calendar = new Calendar("calendar", new AppointmentModel(), options) {
          private static final long serialVersionUID = 8442068089963449950L;
          protected void onInitialize() {
    View Full Code Here

    Examples of com.ibm.icu.util.Calendar

        subscriptionController = new ContextualSubscriptionController(ureq, getWindowControl(), subContext, publisherData);
        mainVC.put("newUsersSubscription", subscriptionController.getInitialComponent());
        Calendar cal = Calendar.getInstance();
        cal.add(Calendar.MONTH, -1);
        dateChooserController = new DateChooserController(ureq, wControl, cal.getTime());
        mainVC.put("dateChooser", dateChooserController.getInitialComponent());
        updateUI(ureq, cal.getTime());
    View Full Code Here

    Examples of com.opengamma.financial.convention.calendar.Calendar

            throw new OpenGammaRuntimeException("Convention with id " + fraNode.getConvention() + " was null");
          throw new OpenGammaRuntimeException("Could not handle underlying convention of type " + convention.getClass());
        final Currency currency = indexConvention.getCurrency();
        final Calendar fixingCalendar = CalendarUtils.getCalendar(_regionSource,
        final Calendar regionCalendar = CalendarUtils.getCalendar(_regionSource,
        final int spotLag = indexConvention.getSettlementDays();
        final BusinessDayConvention businessDayConvention = indexConvention.getBusinessDayConvention();
        final DayCount dayCount = indexConvention.getDayCount();
    View Full Code Here

    Examples of com.saasovation.collaboration.domain.model.calendar.Calendar

                String aCalendarId,
                String aDescription) {

            Tenant tenant = new Tenant(aTenantId);

            Calendar calendar =
                                new CalendarId(aCalendarId));


    View Full Code Here

    Examples of com.sishuok.es.personal.calendar.entity.Calendar

                @RequestParam(value = "end", required = false) @DateTimeFormat(pattern = dataFormat) Date end,
                Model model) {


            Calendar calendar = new Calendar();
            if(start != null) {
                calendar.setLength((int)Math.ceil(1.0 * (end.getTime() - start.getTime()) / oneDayMillis));
                if(DateUtils.isSameDay(start, end)) {
                if(!"00:00:00".equals(DateFormatUtils.format(start, "HH:mm:ss"))) {
                if(!"00:00:00".equals(DateFormatUtils.format(end, "HH:mm:ss"))) {

            model.addAttribute("model", calendar);
            return viewName("newForm");
    View Full Code Here

    Examples of com.smartgwt.client.widgets.calendar.Calendar

            eventDS.setFields(eventIdField, nameField, descField, startDateField, endDateField);

            Calendar calendar = new Calendar();

            return calendar;
    View Full Code Here

    Examples of com.sos.scheduler.model.answers.Calendar

      public Calendar getCalendar() {

        final String conMethodName = conClassName + "::getCalendar";
        Calendar objCalendar = null;
        objCalendar = this.getAnswer().getCalendar();
        return objCalendar;
      } // private Calendar getCalendar
    View Full Code Here
    Copyright © 2018 www.massapi.com. All rights reserved.
    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.