- Util date model java
- Uses of Date in java.security
- Uses of Date in java.security.cert
- Uses of Date in java.sql
- Uses of Date in java.text
- Uses of Date in java.util
- Uses of Date in java.util.concurrent.locks
- Uses of Date in javax.management.openmbean
- Uses of Date in javax.management.timer
- Uses of Date in javax.print.attribute
- Uses of Date in javax.print.attribute.standard
- Uses of Date in javax.security.auth.kerberos
- Uses of Date in javax.security.cert
- Uses of Date in javax.swing
- Uses of Date in javax.xml.datatype
- Util date model java
- Constructor Summary
Util date model java
Provides classes and interfaces for parsing and managing certificates, certificate revocation lists (CRLs), and certification paths.
Provides the API for accessing and processing data stored in a data source (usually a relational database) using the Java TM programming language.
Provides classes and interfaces for handling text, dates, numbers, and messages in a manner independent of natural languages.
Contains the collections framework, legacy collection classes, event model, date and time facilities, internationalization, and miscellaneous utility classes (a string tokenizer, a random-number generator, and a bit array).
Interfaces and classes providing a framework for locking and waiting for conditions that is distinct from built-in synchronization and monitors.
Provides classes and interfaces that describe the types of Java TM Print Service attributes and how they can be collected into attribute sets.
Provides a set of «lightweight» (all-Java language) components that, to the maximum degree possible, work the same on all platforms.
Uses of Date in java.security
Uses of Date in java.security.cert
Returns the invalidity date, as specified in the Invalidity Date extension of this CertificateRevokedException .
Constructs a CertificateRevokedException with the specified revocation date, reason code, authority name, and map of extensions.
Uses of Date in java.sql
A thin wrapper around the java.util.Date class that allows the JDBC API to identify this as an SQL TIME value.
A thin wrapper around java.util.Date that allows the JDBC API to identify this as an SQL TIMESTAMP value.
Uses of Date in java.text
Sets the 100-year period 2-digit years will be interpreted as being in to begin on the date the user specifies.
Uses of Date in java.util
Schedules the specified task for repeated fixed-delay execution, beginning at the specified time.
Uses of Date in java.util.concurrent.locks
| Modifier and Type | Method and Description |
|---|---|
| boolean | AbstractQueuedLongSynchronizer.ConditionObject. awaitUntil (Date deadline) |
Causes the current thread to wait until it is signalled or interrupted, or the specified deadline elapses.
Uses of Date in javax.management.openmbean
| Modifier and Type | Field and Description |
|---|---|
| static SimpleType | SimpleType. DATE |
Uses of Date in javax.management.timer
Creates a new timer notification with the specified type , message and userData and inserts it into the list of notifications with a given date and a null period and number of occurrences.
Creates a new timer notification with the specified type , message and userData and inserts it into the list of notifications with a given date and a null period and number of occurrences.
Creates a new timer notification with the specified type , message and userData and inserts it into the list of notifications with a given date and period and a null number of occurrences.
Creates a new timer notification with the specified type , message and userData and inserts it into the list of notifications with a given date and period and a null number of occurrences.
Creates a new timer notification with the specified type , message and userData and inserts it into the list of notifications with a given date, period and number of occurrences.
Creates a new timer notification with the specified type , message and userData and inserts it into the list of notifications with a given date, period and number of occurrences.
Creates a new timer notification with the specified type , message and userData and inserts it into the list of notifications with a given date, period and number of occurrences.
Creates a new timer notification with the specified type , message and userData and inserts it into the list of notifications with a given date, period and number of occurrences.
Uses of Date in javax.print.attribute
Uses of Date in javax.print.attribute.standard
Uses of Date in javax.security.auth.kerberos
Constructs a KerberosTicket using credentials information that a client either receives from a KDC or reads from a cache.
Uses of Date in javax.security.cert
Uses of Date in javax.swing
Returns a RowFilter that includes entries that have at least one Date value meeting the specified criteria.
Uses of Date in javax.xml.datatype
| Modifier and Type | Method and Description |
|---|---|
| void | Duration. addTo (Date date) |
Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2023, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.
Util date model java
The class Date represents a specific instant in time, with millisecond precision. Prior to JDK 1.1, the class Date had two additional functions. It allowed the interpretation of dates as year, month, day, hour, minute, and second values. It also allowed the formatting and parsing of date strings. Unfortunately, the API for these functions was not amenable to internationalization. As of JDK 1.1, the Calendar class should be used to convert between dates and time fields and the DateFormat class should be used to format and parse date strings. The corresponding methods in Date are deprecated. Although the Date class is intended to reflect coordinated universal time (UTC), it may not do so exactly, depending on the host environment of the Java Virtual Machine. Nearly all modern operating systems assume that 1 day = 24 × 60 × 60 = 86400 seconds in all cases. In UTC, however, about once every year or two there is an extra second, called a «leap second.» The leap second is always added as the last second of the day, and always on December 31 or June 30. For example, the last minute of the year 1995 was 61 seconds long, thanks to an added leap second. Most computer clocks are not accurate enough to be able to reflect the leap-second distinction. Some computer standards are defined in terms of Greenwich mean time (GMT), which is equivalent to universal time (UT). GMT is the «civil» name for the standard; UT is the «scientific» name for the same standard. The distinction between UTC and UT is that UTC is based on an atomic clock and UT is based on astronomical observations, which for all practical purposes is an invisibly fine hair to split. Because the earth’s rotation is not uniform (it slows down and speeds up in complicated ways), UT does not always flow uniformly. Leap seconds are introduced as needed into UTC so as to keep UTC within 0.9 seconds of UT1, which is a version of UT with certain corrections applied. There are other time and date systems as well; for example, the time scale used by the satellite-based global positioning system (GPS) is synchronized to UTC but is not adjusted for leap seconds. An interesting source of further information is the United States Naval Observatory (USNO):
- A year y is represented by the integer y — 1900 .
- A month is represented by an integer from 0 to 11; 0 is January, 1 is February, and so forth; thus 11 is December.
- A date (day of month) is represented by an integer from 1 to 31 in the usual manner.
- An hour is represented by an integer from 0 to 23. Thus, the hour from midnight to 1 a.m. is hour 0, and the hour from noon to 1 p.m. is hour 12.
- A minute is represented by an integer from 0 to 59 in the usual manner.
- A second is represented by an integer from 0 to 61; the values 60 and 61 occur only for leap seconds and even then only in Java implementations that actually track leap seconds correctly. Because of the manner in which leap seconds are currently introduced, it is extremely unlikely that two leap seconds will occur in the same minute, but this specification follows the date and time conventions for ISO C.
In all cases, arguments given to methods for these purposes need not fall within the indicated ranges; for example, a date may be specified as January 32 and is interpreted as meaning February 1.
Constructor Summary
Allocates a Date object and initializes it so that it represents the time at which it was allocated, measured to the nearest millisecond.
As of JDK version 1.1, replaced by Calendar.set(year + 1900, month, date) or GregorianCalendar(year + 1900, month, date) .
As of JDK version 1.1, replaced by Calendar.set(year + 1900, month, date, hrs, min) or GregorianCalendar(year + 1900, month, date, hrs, min) .
As of JDK version 1.1, replaced by Calendar.set(year + 1900, month, date, hrs, min, sec) or GregorianCalendar(year + 1900, month, date, hrs, min, sec) .
Allocates a Date object and initializes it to represent the specified number of milliseconds since the standard base time known as «the epoch», namely January 1, 1970, 00:00:00 GMT.