Examples of XmlCalendar

• org.apache.ode.utils.xsd.XMLCalendar
  XML schema aware calendar : capable of parsing xml schema string of form CCYY-MM-DDThh:mm:ss.ss
• org.apache.xmlbeans.XmlCalendar
  An XML Schema compatible subclass of {@link java.util.GregorianCalendar GregorianCalendar}. XmlCalendar modifies several key details in the behavior of GregorianCalendar to make it more useful when dealing with XML dates.

  It is easy to convert between XmlCalendar and {@link GDate}, or to parse or emit an XmlCalendar using a standard XML Schema lexical representation.

  1. To match XML Schema dates, this XmlCalendar is a fully proleptic Gregorian calendar by default, which means that Gregorian calendar rules are applied backwards in time as if they had always been in effect, actual historical circumstances concerning the observance of the 1582 decree of Pope Gregory XIII notwithstanding.
  2. In order to better support partially-specified dates for XML Schema, this implementation provides a stable get(field) method that does not modify the instance if you are acessing a field right after it was explicitly set: a set followed by a get will always return the same thing and will not fill in any other fields. However, if you get a field that was not explicitly set, then all the fields are still automatically filled and normalized for you, just like a regular GregorianCalendar. If you wish to force the completion and defaulting of all the fields (without hunting to get one that happens to be unset), you can always do so by calling getTime().
  3. When a year is unspecified and needs to be filled in automatically (for example when using a .get or .getTime method as discussed above), the year is defaulted to year 0 (also known as 1 BC). This is different from {@link GregorianCalendar}, which chooses 1970. The reason 0 is preferable is that it is a leap year and so it permits the date --2-29 to be specified stably. A different default year can be chosen via the static method {@link #setDefaultYear(int) XmlCalendar.setDefaultYear()}, or by setting the system property "user.defaultyear". If you do change this value, you should pick another leap year such as 2000 and avoid non-leap years such as 1900.
  4. When constructing an XmlCalendar from an XML Schema formatted date or time string or GDate object, the timezone for the calendar is taken from the string if it is present, or taken to be {@link java.util.TimeZone#getDefault() TimeZone.getDefault()} if not.

     For example, the XML timezone "Z" is translated to "GMT"; the XML timezone "+05:00" is translated to "GMT+05:00".

  5. Finally, this implementation provides a String constructor and a toString() method that comply with the XML Schema conventions for formatting a date. If only a subset of fields have been explicitly set, toString() produces a string with the proper subset of information.
• org.eclipse.emf.ecore.xml.type.internal.XMLCalendar
  3.org/TR/2001/REC-xmlschema-2-20010502/">W3C XML Schema 1.0 dateTime, time, date, gYearMonth, gYear, gMonthDay, gDay, gMonth data types.

  NOTE: this class is for internal use only.

Examples of org.eclipse.emf.ecore.xml.type.internal.XMLCalendar

Examples of org.eclipse.emf.ecore.xml.type.internal.XMLCalendar