Building block class for an immutable date-time, with no time zone.

<P>

This class is provided as an alternative to java.util.{@link java.util.Date}.

You're strongly encouraged to use this class in your WEB4J applications, but you can still use java.util.{@link java.util.Date} if you wish.

   <li>a date-and-time : <tt>1958-03-31 18:59:56.123456789</tt>

   <li>a date only : <tt>1958-03-31</tt>

   <li>a time only : <tt>18:59:56.123456789</tt>

</ul>

<P>

<a href='#Examples'>Examples</a><br>

<a href='#JustificationForThisClass'>Justification For This Class</a><br>

<a href='#DatesAndTimesInGeneral'>Dates and Times In General</a><br>

<a href='#TheApproachUsedByThisClass'>The Approach Used By This Class</a><br>

<a href='#TwoSetsOfOperations'>Two Sets Of Operations</a><br>

<a href='#ParsingDateTimeAcceptedFormats'>Parsing DateTime - Accepted Formats</a><br>

<a href='#FormattingLanguage'>Mini-Language for Formatting</a><br>

<a href='#InteractionWithTimeSource'>Interaction with {@link TimeSource}</a><br>

<a href='#PassingDateTimeToTheDatabase'>Passing DateTime Objects to the Database</a>

<a name='Examples'></a>

<h3> Examples</h3>

Some quick examples of using this class :

<PRE>

  DateTime dateAndTime = new DateTime("2010-01-19 23:59:59");

  //highest precision is nanosecond, not millisecond:

  DateTime dateAndTime = new DateTime("2010-01-19 23:59:59.123456789");

 

  DateTime dateOnly = new DateTime("2010-01-19");

  DateTime timeOnly = new DateTime("23:59:59");

 

  DateTime dateOnly = DateTime.forDateOnly(2010,01,19);

  DateTime timeOnly = DateTime.forTimeOnly(23,59,59,0);

 

  DateTime dt = new DateTime("2010-01-15 13:59:15");

  boolean leap = dt.isLeapYear(); //false

  dt.getNumDaysInMonth(); //31

  dt.getStartOfMonth(); //2010-01-01, 00:00:00

  dt.getEndOfDay(); //2010-01-15, 23:59:59

  dt.format("YYYY-MM-DD"); //formats as '2010-01-15'

  dt.plusDays(30); //30 days after Jan 15

  dt.numDaysFrom(someDate); //returns an int

  dueDate.lt(someDate); //less-than

  dueDate.lteq(someDate); //less-than-or-equal-to

 

  //{@link ActionImpl#getTimeZone()} is readily available in most Actions

  DateTime.now(getTimeZone());

  DateTime.today(getTimeZone());

  DateTime fromMilliseconds = DateTime.forInstant(31313121L, getTimeZone());

  birthday.isInFuture(getTimeZone());

</PRE>

<a name='JustificationForThisClass'></a>

<h3> Justification For This Class</h3>

The fundamental reasons why this class exists are :

<ul>

<li>to avoid the embarrassing number of distasteful inadequacies in the JDK's date classes

<li>to oppose the very "mental model" of the JDK's date-time classes with something significantly simpler

</ul>

<a name='MentalModels'></a>

<P><b>There are 2 distinct mental models for date-times, and they don't play well together</b> :

<ul>

<li><b>timeline</b> - an instant on the timeline, as a physicist would picture it, representing the number of

seconds from some epoch. In this picture, such a date-time can have many, many different

representations according to calendar and time zone. That is, the date-time, <i> as seen and understood by

the end user</i>, can change according to "who's looking at it". It's important to understand that a timeline instant,

before being presented to the user, <i>must always have an associated time zone - even in the case of

a date only, with no time.</i>

<li><b>everyday</b> - a date-time in the Gregorian calendar, such as '2009-05-25 18:25:00',

which never changes according to "who's looking at it". Here, <i>the time zone is always both implicit and immutable</i>.

</ul>

<P>The problem is that java.util.{@link java.util.Date} uses <i>only</i> the timeline style, while <i>most</i> users, <i>most</i>

of the time, think in terms of the <i>other</i> mental model - the 'everday' style.

In particular, there are a large number of applications which experience

<a href='http://martinfowler.com/bliki/TimeZoneUncertainty.html'>problems with time zones</a>, because the timeline model

is used instead of the everday model.

<i>Such problems are often seen by end users as serious bugs, because telling people the wrong date or time is often a serious issue.</i>

<b>These problems make you look stupid.</b>

<a name='JDKDatesMediocre'></a>

<h4>Date Classes in the JDK are Mediocre</h4>

The JDK's classes related to dates are widely regarded as frustrating to work with, for various reasons:

<ul>

<li>mistakes regarding time zones are very common

<li>month indexes are 0-based, leading to off-by-one errors

<li>difficulty of calculating simple time intervals

<li><tt>java.util.Date</tt> is mutable, but 'building block' classes should be

immutable

<li>numerous other minor nuisances

</ul>

<a name='JodaTimeDrawbacks'></a>

<h4>Joda Time Has Drawbacks As Well</h4>

The <a href='http://joda-time.sourceforge.net/'>Joda Time</a> library is used by some programmers as an alternative

to the JDK classes. Joda Time has the following drawbacks :

<ul>

<li>it limits precision to milliseconds. Database timestamp values almost always have a precision of microseconds

or even nanoseconds. This is a serious defect: <b>a library should never truncate your data, for any reason.</b>

<li>it's large, with well over 100 items in its <a href='http://joda-time.sourceforge.net/api-release/index.html'>javadoc</a>

<li>in order to stay current, it needs to be manually updated occasionally with fresh time zone data

<li>it has mutable versions of classes

<li>it always coerces March 31 + 1 Month to April 30 (for example), without giving you any choice in the matter

<li>some databases allow invalid date values such as '0000-00-00', but Joda Time doesn't seem to be able to handle them  

</ul>

<a name='DatesAndTimesInGeneral'></a>

<h3>Dates and Times in General</h3>

<h4>Civil Timekeeping Is Complex</h4>

Civil timekeeping is a byzantine hodge-podge of arcane and arbitrary rules. Consider the following :

<ul>

<li>months have varying numbers of days

<li>one month (February) has a length which depends on the year

<li>not all years have the same number of days

<li>time zone rules spring forth arbitrarily from the fecund imaginations of legislators

<li>summer hours mean that an hour is 'lost' in the spring, while another hour must

repeat itself in the autumn, during the switch back to normal time

<li>summer hour logic varies widely across various jurisdictions

<li>the cutover from the Julian calendar to the Gregorian calendar happened at different times in

different places, which causes a varying number of days to be 'lost' during the cutover

<li>occasional insertion of leap seconds are used to ensure synchronization with the

rotating Earth (whose speed of rotation is gradually slowing down, in an irregular way)

<li>there is no year 0 (1 BC is followed by 1 AD), except in the reckoning used by

astronomers

</ul>

<h4>How Databases Treat Dates</h4>

<b>Most databases model dates and times using the Gregorian Calendar in an aggressively simplified form</b>,

in which :

<ul>

<li>the Gregorian calendar is extended back in time as if it was in use previous to its

inception (the 'proleptic' Gregorian calendar)

<li>the transition between Julian and Gregorian calendars is entirely ignored

<li>leap seconds are entirely ignored

<li>summer hours are entirely ignored

<li>often, even time zones are ignored, in the sense that <i>the underlying database

column doesn't usually explicitly store any time zone information</i>.

</ul>

<P><a name='NoTimeZoneInDb'></a>The final point requires elaboration.

Some may doubt its veracity, since they have seen date-time information "change time zone" when

retrieved from a database. But this sort of change is usually applied using logic which is <i>external</i> to the data

stored in the particular column. 

<P> For example, the following items might be used in the calculation of a time zone difference :

<ul>

<li>time zone setting for the client (or JDBC driver)

<li>time zone setting for the client's connection to the database server

<li>time zone setting of the database server

<li>time zone setting of the host where the database server resides

</ul>

<P>(Note as well what's <i>missing</i> from the above list: your own application's logic, and the user's time zone preference.)

<P>When an end user sees such changes to a date-time, all they will say to you is

<i>"Why did you change it? That's not what I entered"</i> - and this is a completely valid question.

Why <i>did</i> you change it? Because you're using the timeline model instead of the everyday model.

Perhaps you're using a inappropriate abstraction for what the user really wants.

<a name='TheApproachUsedByThisClass'></a>

<h3>The Approach Used By This Class</h3>

This class takes the following design approach :

<ul>

<li>it models time in the "everyday" style, not in the "timeline" style (see <a href='#MentalModels'>above</a>)

<li>its precision matches the highest precision used by databases (nanosecond)

<li>it uses only the proleptic Gregorian Calendar, over the years <tt>1..9999</tt>

<li><i>it ignores all non-linearities</i>: summer-hours, leap seconds, and the cutover

from Julian to Gregorian calendars

<li><i>it ignores time zones</i>. Most date-times are stored in columns whose type

does <i>not</i> include time zone information (see note <a href='#NoTimeZoneInDb'>above</a>).

<li>it has (very basic) support for wonky dates, such as the magic value <tt>0000-00-00</tt> used by MySQL

<li>it's immutable

<li>it lets you choose among 4 policies for 'day overflow' conditions during calculations

<li>it talks to your {@link TimeSource} implementation when returning the current moment, allowing you to customise dates during testing

</ul>

<P>Even though the above list may appear restrictive, it's very likely true that

<tt>DateTime</tt> can handle the dates and times you're currently storing in your database.

<a name='TwoSetsOfOperations'></a>

<h3>Two Sets Of Operations</h3>

This class allows for 2 sets of operations: a few "basic" operations, and many "computational" ones.

<P><b>Basic operations</b> model the date-time as a simple, dumb String, with absolutely no parsing or substructure.

This will always allow your application to reflect exactly what is in a <tt>ResultSet</tt>, with

absolutely no modification for time zone, locale, or for anything else.

<P>This is meant as a back-up, to ensure that <i>your application will always be able

to, at the very least, display a date-time exactly as it appears in your

<tt>ResultSet</tt> from the database</i>. This style is particularly useful for handling invalid

dates such as <tt>2009-00-00</tt>, which can in fact be stored by some databases (MySQL, for

example). It can also be used to handle unusual items, such as MySQL's

<a href='http://dev.mysql.com/doc/refman/5.1/en/time.html'>TIME</a> datatype.

<P>The basic operations are represented by {@link #DateTime(String)}, {@link #toString()}, and {@link #getRawDateString()}.

<P><b>Computational operations</b> allow for calculations and formatting.

If a computational operation is performed by this class (for example, if the caller asks for the month),

then any underlying date-time String must be parseable by this class into its components - year, month, day, and so on.

Computational operations require such parsing, while the basic operations do not. Almost all methods in this class

are categorized as computational operations.

<a name="ParsingDateTimeAcceptedFormats"></a>

<h3>Parsing DateTime - Accepted Formats</h3>

  The {@link #DateTime(String)} constructor accepts a <tt>String</tt> representation of a date-time.

The format of the String can take a number of forms. When retrieving date-times from a database, the

majority of cases will have little problem in conforming to these formats. If necessary, your SQL statements

can almost always use database formatting functions to generate a String whose format conforms to one of the

many formats accepted by the {@link #DateTime(String)} constructor. 

<a name="FormattingLanguage"></a>

<h3>Mini-Language for Formatting</h3>

This class defines a simple mini-language for formatting a <tt>DateTime</tt>, used by the various <tt>format</tt> methods.

<P>The following table defines the symbols used by this mini-language, and the corresponding text they

would generate given the date:

<PRE>1958-04-09 Wednesday, 03:05:06.123456789 AM</PRE>

in an English Locale. (Items related to date are in upper case, and items related to time are in lower case.)

<P><table border='1' cellpadding='3' cellspacing='0'>

<tr><th>Format</th><th>Output</th> <th>Description</th><th>Needs Locale?</th></tr>

<tr><td>YYYY</td> <td>1958</td> <td>Year</td><td>...</td></tr>

<tr><td>YY</td> <td>58</td> <td>Year without century</td><td>...</td></tr>

<tr><td>M</td> <td>4</td> <td>Month 1..12</td><td>...</td></tr>

<tr><td>MM</td> <td>04</td> <td>Month 01..12</td><td>...</td></tr>

<tr><td>MMM</td> <td>Apr</td> <td>Month Jan..Dec</td><td>Yes</td></tr>

<tr><td>MMMM</td> <td>April</td> <td>Month January..December</td><td>Yes</td></tr>

<tr><td>DD</td> <td>09</td> <td>Day 01..31</td><td>...</td></tr>

<tr><td>D</td> <td>9</td> <td>Day 1..31</td><td>...</td></tr>

<tr><td>WWWW</td> <td>Wednesday</td> <td>Weekday Sunday..Saturday</td><td>Yes</td></tr>

<tr><td>WWW</td> <td>Wed</td> <td>Weekday Sun..Sat</td><td>Yes</td></tr>

<tr><td>hh</td> <td>03</td> <td>Hour 01..23</td><td>...</td></tr>

<tr><td>h</td> <td>3</td> <td>Hour 1..23</td><td>...</td></tr>

<tr><td>hh12</td> <td>03</td> <td>Hour 01..12</td><td>...</td></tr>

<tr><td>h12</td> <td>3</td> <td>Hour 1..12</td><td>...</td></tr>

<tr><td>a</td> <td>AM</td> <td>AM/PM Indicator</td><td>Yes</td></tr>

<tr><td>mm</td> <td>05</td> <td>Minutes 01..59</td><td>...</td></tr>

<tr><td>m</td> <td>5</td> <td>Minutes 1..59</td><td>...</td></tr>

<tr><td>ss</td> <td>06</td> <td>Seconds 01..59</td><td>...</td></tr>

<tr><td>s</td> <td>6</td> <td>Seconds 1..59</td><td>...</td></tr>

<tr><td>f</td> <td>1</td> <td>Fractional Seconds, 1 decimal</td><td>...</td></tr>

<tr><td>ff</td> <td>12</td> <td>Fractional Seconds, 2 decimals</td><td>...</td></tr>

<tr><td>fff</td> <td>123</td> <td>Fractional Seconds, 3 decimals</td><td>...</td></tr>

<tr><td>ffff</td> <td>1234</td> <td>Fractional Seconds, 4 decimals</td><td>...</td></tr>

<tr><td>fffff</td> <td>12345</td> <td>Fractional Seconds, 5 decimals</td><td>...</td></tr>

<tr><td>ffffff</td> <td>123456</td> <td>Fractional Seconds, 6 decimals</td><td>...</td></tr>

<tr><td>fffffff</td> <td>1234567</td> <td>Fractional Seconds, 7 decimals</td><td>...</td></tr>

<tr><td>ffffffff</td> <td>12345678</td> <td>Fractional Seconds, 8 decimals</td><td>...</td></tr>

<tr><td>fffffffff</td> <td>123456789</td> <td>Fractional Seconds, 9 decimals</td><td>...</td></tr>

<tr><td>|</td> <td>(no example)</td> <td>Escape character</td><td>...</td></tr>

</table>

<P>As indicated above, some of these symbols can only be used with an accompanying <tt>Locale</tt>.

In general, if the output is text, not a number, then a <tt>Locale</tt> will be needed.

For example, 'September' is localizable text, while '09' is a numeric representation, which doesn't require a <tt>Locale</tt>.

Thus, the symbol 'MM' can be used without a <tt>Locale</tt>, while 'MMMM' and 'MMM' both require a <tt>Locale</tt>, since they

generate text, not a number.

<P>The fractional seconds 'f' does not perform any rounding. The escape character '|' allows you

to insert arbitrary text. 

<P>Examples :

<table border='1' cellpadding='3' cellspacing='0'>

<tr><th>Format</th><th>Output</th></tr>

<tr><td>YYYY-MM-DD hh:mm:ss.fffffffff a</td> <td>1958-04-09 03:05:06.123456789 AM</td></tr>

<tr><td>YYYY-MM-DD hh:mm:ss.fff a</td> <td>1958-04-09 03:05:06.123 AM</td></tr>

<tr><td>YYYY-MM-DD</td> <td>1958-04-09</td></tr>

<tr><td>hh:mm:ss.fffffffff</td> <td>03:05:06.123456789</td></tr>

<tr><td>hh:mm:ss</td> <td>03:05:06</td></tr>

<tr><td>YYYY-M-D h:m:s</td> <td>1958-4-9 3:5:6</td></tr>

<tr><td>WWWW, MMMM D, YYYY</td> <td>Wednesday, April 9, 1958</td></tr>

<tr><td>WWWW, MMMM D, YYYY |at| D a</td> <td>Wednesday, April 9, 1958 at 3 AM</td></tr>

</table>

<a name='InteractionWithTimeSource'></a>

<h3>Interaction with {@link TimeSource}</h3>

The methods of this class related to the current date interact with your configured implementation

of {@link hirondelle.web4j.util.TimeSource}. That is, {@link #now(TimeZone)} and {@link #today(TimeZone)}

will return values derived from {@link TimeSource}. Thus, callers of this class automatically use any

'fake' system clock that you may want to define.

<a name='PassingDateTimeToTheDatabase'></a>

<h3>Passing DateTime Objects to the Database</h3>

When a <tt>DateTime</tt> is passed as a parameter to an SQL statement, the <tt>DateTime</tt> is

formatted into a <tt>String</tt> of a form accepted by the database. There are two mechanisms to

accomplish this

<ul>

   <li>in your DAO code, format the <tt>DateTime</tt> explicitly as a String, using one of the <tt>format</tt> methods,

   and pass the <tt>String</tt> as the parameter to the SQL statement, and not the actual <tt>DateTime</tt>

   <li>pass the <tt>DateTime</tt> itself. In this case, WEB4J will use the setting in <tt>web.xml</tt> named

   <tt>DateTimeFormatForPassingParamsToDb</tt> to perform the formatting for you. If the formats defined by this

   setting are not appropriate for a given case, you will need to format the <tt>DateTime</tt> as a String explicitly instead.

</ul>

*/

  /** The seven parts of a <tt>DateTime</tt> object. The <tt>DAY</tt> represents the day of the month (1..31), not the weekday. */

  public enum Unit {

    YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, NANOSECONDS;

  }

  /**

   Policy for treating 'day-of-the-month overflow' conditions encountered during some date calculations.

  

   <P>Months are different from other units of time, since the length of a month is not fixed, but rather varies with

   both month and year. This leads to problems. Take the following simple calculation, for example :

  

   <PRE>May 31 + 1 month = ?</PRE>

  

   <P>What's the answer? Since there is no such thing as June 31, the result of this operation is inherently ambiguous.

   This  <tt>DayOverflow</tt> enumeration lists the various policies for treating such situations, as supported by

   <tt>DateTime</tt>.

  

   <P>This table illustrates how the policies behave :

   <P><table BORDER="1" CELLPADDING="3" CELLSPACING="0">

   <tr>

   <th>Date</th>

   <th>DayOverflow</th>

   <th>Result</th>

   </tr>   

   <tr>

   <td>May 31 + 1 Month</td>

   <td>LastDay</td>

   <td>June 30</td>

   </tr>   

   <tr>

   <td>May 31 + 1 Month</td>

   <td>FirstDay</td>

   <td>July 1</td>

   </tr>   

   <tr>

   <td>December 31, 2001 + 2 Months</td>

   <td>Spillover</td>

   <td>March 3</td>

   </tr>   

   <tr>

   <td>May 31 + 1 Month</td>

   <td>Abort</td>

   <td>RuntimeException</td>

   </tr>   

   </table>

   */

  public enum DayOverflow {

    /** Coerce the day to the last day of the month. */

    LastDay,

    /** Coerce the day to the first day of the next month. */

    FirstDay,

    /** Spillover the day into the next month. */

    Spillover,

    /** Throw a RuntimeException. */

    Abort;

  }

  /**

   Constructor taking a date-time as a String.

  

   <P>This constructor is called when WEB4J's data layer needs to translate a column in a <tt>ResultSet</tt>

   into a <tt>DateTime</tt>.

  

   <P> When this constructor is called, the underlying text can be in an absolutely arbitrary

   form, since it will not, initially, be parsed in any way. This policy of extreme

   leniency allows you to use dates in an arbitrary format, without concern over possible

   transformations of the date (time zone in particular), and without concerns over possibly bizarre content, such

   as '2005-00-00', as seen in some databases, such as MySQL.

  

   <P><i>However</i>, the moment you attempt to call <a href='#TwoSetsOfOperations'>almost any method</a>

   in this class, an attempt will be made to parse

   the given date-time string into its constituent parts. Then, if the date-time string does not match one of the

   example formats listed below, a <tt>RuntimeException</tt> will be thrown.

  

   <P>The full date format expected by this class is <tt>'YYYY-MM-YY hh:mm:ss.fffffffff'</tt>.

   All fields except for the fraction of a second have a fixed width.

   In addition, various portions of this format are also accepted by this class.

  

   <P>All of the following dates can be parsed by this class to make a <tt>DateTime</tt> :

   <ul>

   <li><tt>2009-12-31 00:00:00.123456789</tt>

   <li><tt>2009-12-31 00:00:00.12345678</tt>

   <li><tt>2009-12-31 00:00:00.1234567</tt>

   <li><tt>2009-12-31 00:00:00.123456</tt>

   <li><tt>2009-12-31 23:59:59.12345</tt>

   <li><tt>2009-01-31 16:01:01.1234</tt>

   <li><tt>2009-01-01 16:59:00.123</tt>

   <li><tt>2009-01-01 16:00:01.12</tt>

   <li><tt>2009-02-28 16:25:17.1</tt>

   <li><tt>2009-01-01 00:01:01</tt>

   <li><tt>2009-01-01 16:01</tt>

   <li><tt>2009-01-01 16</tt>

   <li><tt>2009-01-01</tt>

   <li><tt>2009-01</tt>

   <li><tt>2009</tt>

   <li><tt>0009</tt>

   <li><tt>9</tt>

   <li><tt>00:00:00.123456789</tt>

   <li><tt>00:00:00.12345678</tt>

   <li><tt>00:00:00.1234567</tt>

   <li><tt>00:00:00.123456</tt>

   <li><tt>23:59:59.12345</tt>

   <li><tt>01:59:59.1234</tt>

   <li><tt>23:01:59.123</tt>

   <li><tt>00:00:00.12</tt>

   <li><tt>00:59:59.1</tt>

   <li><tt>23:59:00</tt>

   <li><tt>23:00:10</tt>

   <li><tt>00:59</tt>

   </ul>

  

   <P>The range of each field is :

   <ul>

   <li>year: 1..9999

   <li>month: 01..12

   <li>day: 01..31

   <li>hour: 00..23

   <li>minute: 00..59

   <li>second: 00..59

   <li>nanosecond: 0..999999999

   </ul>

  

   <P>Note that <b>database format functions</b> are an option when dealing with date formats.

   Since your application is always in control of the SQL used to talk to the database, you can, if needed, usually

    use database format functions to alter the format of dates returned in a <tt>ResultSet</tt>.

   */

  public DateTime(String aDateTime) {

    fIsAlreadyParsed = false;

    if (aDateTime == null) {

      throw new IllegalArgumentException("String passed to DateTime constructor is null. You can use an empty string, but not a null reference.");

    }

    fDateTime = aDateTime;

  }

  /**

   Constructor taking each time unit explicitly.

  

   <P>Although all parameters are optional, many operations on this class require year-month-day to be

   present.

  

   @param aYear 1..9999, optional

   @param aMonth 1..12 , optional

   @param aDay 1..31, cannot exceed the number of days in the given month/year, optional

   @param aHour 0..23, optional

   @param aMinute 0..59, optional

   @param aSecond 0..59, optional

   @param aNanoseconds 0..999,999,999, optional (allows for databases that store timestamps up to

   nanosecond precision).

   */

  public DateTime(Integer aYear, Integer aMonth, Integer aDay, Integer aHour, Integer aMinute, Integer aSecond, Integer aNanoseconds) {

    fIsAlreadyParsed = true;

    fYear = aYear;

    fMonth = aMonth;

    fDay = aDay;

    fHour = aHour;

    fMinute = aMinute;

    fSecond = aSecond;

    fNanosecond = aNanoseconds;

    validateState();

  }

  /**

   Factory method returns a <tt>DateTime</tt> having year-month-day only, with no time portion.

   <P>See {@link #DateTime(Integer, Integer, Integer, Integer, Integer, Integer, Integer)} for constraints on the parameters.

   */

  public static DateTime forDateOnly(Integer aYear, Integer aMonth, Integer aDay) {

    return new DateTime(aYear, aMonth, aDay, null, null, null, null);

  }

  /**

   Factory method returns a <tt>DateTime</tt> having hour-minute-second-nanosecond only, with no date portion.

   <P>See {@link #DateTime(Integer, Integer, Integer, Integer, Integer, Integer, Integer)} for constraints on the parameters.

   */

  public static DateTime forTimeOnly(Integer aHour, Integer aMinute, Integer aSecond, Integer aNanoseconds) {

    return new DateTime(null, null, null, aHour, aMinute, aSecond, aNanoseconds);

  }

  /**

   Constructor taking a millisecond value and a {@link TimeZone}.

   This constructor may be use to convert a <tt>java.util.Date</tt> into a <tt>DateTime</tt>.

  

   <P>Unfortunately, only millisecond precision is possible for this method.

  

   @param aMilliseconds must be in the range corresponding to the range of dates supported by this class (year 1..9999); corresponds

   to a millisecond instant on the timeline, measured from the epoch used by {@link java.util.Date}.

   */

  public static DateTime forInstant(long aMilliseconds, TimeZone aTimeZone) {

    Calendar calendar = new GregorianCalendar(aTimeZone);

    calendar.setTimeInMillis(aMilliseconds);

    int year = calendar.get(Calendar.YEAR);

    int month = calendar.get(Calendar.MONTH) + 1; // 0-based

    int day = calendar.get(Calendar.DAY_OF_MONTH);

    int hour = calendar.get(Calendar.HOUR_OF_DAY); // 0..23

    int minute = calendar.get(Calendar.MINUTE);

    int second = calendar.get(Calendar.SECOND);

    int milliseconds = calendar.get(Calendar.MILLISECOND);

    int nanoseconds = milliseconds * 1000 * 1000;

    return new DateTime(year, month, day, hour, minute, second, nanoseconds);

  }

 

  /**

    For the given time zone,  return the corresponding time in milliseconds for this <tt>DateTime</tt>.

   

    <P>This method is meant to help you convert between a <tt>DateTime</tt> and the

    JDK's date-time classes, which are based on the combination of a time zone and a

    millisecond value from the Java epoch.

    <P>Since <tt>DateTime</tt> can go to nanosecond accuracy, the return value can

    lose precision. The nanosecond value is truncated to milliseconds, not rounded.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

  */

  public long getMilliseconds(TimeZone aTimeZone){

    Integer year = getYear();

    Integer month = getMonth();

    Integer day = getDay();

    //coerce missing times to 0:

    Integer hour = getHour() == null ? 0 : getHour();

    Integer minute = getMinute() == null ? 0 : getMinute();

    Integer second = getSecond() == null ? 0 : getSecond();

    Integer nanos = getNanoseconds() == null ? 0 : getNanoseconds();

   

    Calendar calendar = new GregorianCalendar(aTimeZone);

    calendar.set(Calendar.YEAR, year);

    calendar.set(Calendar.MONTH, month-1); // 0-based

    calendar.set(Calendar.DAY_OF_MONTH, day);

    calendar.set(Calendar.HOUR_OF_DAY, hour); // 0..23

    calendar.set(Calendar.MINUTE, minute);

    calendar.set(Calendar.SECOND, second);

    calendar.set(Calendar.MILLISECOND, nanos/1000000);

   

    return calendar.getTimeInMillis();

  }

  /**

   Return the raw date-time String passed to the {@link #DateTime(String)} constructor.

   Returns <tt>null</tt> if that constructor was not called. See {@link #toString()} as well.

   */

  public String getRawDateString() {

    return fDateTime;

  }

  /** Return the year, 1..9999. */

  public Integer getYear() {

    ensureParsed();

    return fYear;

  }

  /** Return the Month, 1..12. */

  public Integer getMonth() {

    ensureParsed();

    return fMonth;

  }

  /** Return the Day of the Month, 1..31. */

  public Integer getDay() {

    ensureParsed();

    return fDay;

  }

  /** Return the Hour, 0..23. */

  public Integer getHour() {

    ensureParsed();

    return fHour;

  }

  /** Return the Minute, 0..59. */

  public Integer getMinute() {

    ensureParsed();

    return fMinute;

  }

  /** Return the Second, 0..59. */

  public Integer getSecond() {

    ensureParsed();

    return fSecond;

  }

  /** Return the Nanosecond, 0..999999999. */

  public Integer getNanoseconds() {

    ensureParsed();

    return fNanosecond;

  }

  /**

   Return the Modified Julian Day Number.

   <P>The Modified Julian Day Number is defined by astronomers for simplifying the calculation of the number of days between 2 dates.

   Returns a monotonically increasing sequence number.

   Day 0 is November 17, 1858 00:00:00 (whose Julian Date was 2400000.5).

  

   <P>Using the Modified Julian Day Number instead of the Julian Date has 2 advantages:

   <ul>

   <li>it's a smaller number

   <li>it starts at midnight, not noon (Julian Date starts at noon)

   </ul>

  

   <P>Does not reflect any time portion, if present.

  

   <P>(In spite of its name, this method, like all other methods in this class, uses the

   proleptic Gregorian calendar - not the Julian calendar.)

  

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public Integer getModifiedJulianDayNumber() {

    ensureHasYearMonthDay();

    int result = calculateJulianDayNumberAtNoon() - 1 - EPOCH_MODIFIED_JD;

    return result;

  }

  /**

   Return an index for the weekday for this <tt>DateTime</tt>.

   Returns 1..7 for Sunday..Saturday.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public Integer getWeekDay() {

    ensureHasYearMonthDay();

    int dayNumber = calculateJulianDayNumberAtNoon() + 1;

    int index = dayNumber % 7;

    return index + 1;

  }

  /**

   Return an integer in the range 1..366, representing a count of the number of days from the start of the year.

   January 1 is counted as day 1.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public Integer getDayOfYear() {

    ensureHasYearMonthDay();

    int k = isLeapYear() ? 1 : 2;

    Integer result = ((275 * fMonth) / 9) - k * ((fMonth + 9) / 12) + fDay - 30; // integer division

    return result;

  }

  /**

   Returns true only if the year is a leap year.

   <P>Requires year to be present; if not, a runtime exception is thrown.

   */

  public Boolean isLeapYear() {

    ensureParsed();

    Boolean result = null;

    if (isPresent(fYear)) {

      result = isLeapYear(fYear);

    }

    else {

      throw new MissingItem("Year is absent. Cannot determine if leap year.");

    }

    return result;

  }

  /**

   Return the number of days in the month which holds this <tt>DateTime</tt>.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public int getNumDaysInMonth() {

    ensureHasYearMonthDay();

    return getNumDaysInMonth(fYear, fMonth);

  }

  /**

   Return The week index of this <tt>DateTime</tt> with respect to a given starting <tt>DateTime</tt>.

   <P>The single parameter to this method defines first day of week number 1.

   See {@link #getWeekIndex()} as well.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public Integer getWeekIndex(DateTime aStartingFromDate) {

    ensureHasYearMonthDay();

    aStartingFromDate.ensureHasYearMonthDay();

    int diff = getModifiedJulianDayNumber() - aStartingFromDate.getModifiedJulianDayNumber();

    return (diff / 7) + 1; // integer division

  }

  /**

   Return The week index of this <tt>DateTime</tt>, taking day 1 of week 1 as Sunday, January 2, 2000.

   <P>See {@link #getWeekIndex(DateTime)} as well, which takes an arbitrary date to define

   day 1 of week 1.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public Integer getWeekIndex() {

    DateTime start = DateTime.forDateOnly(2000, 1, 2);

    return getWeekIndex(start);

  }

  /**

   Return <tt>true</tt> only if this <tt>DateTime</tt> has the same year-month-day as the given parameter.

   Time is ignored by this method.

   <P> Requires year-month-day to be present, both for this <tt>DateTime</tt> and for

   <tt>aThat</tt>; if not, a runtime exception is thrown.

   */

  public boolean isSameDayAs(DateTime aThat) {

    boolean result = false;

    ensureHasYearMonthDay();

    aThat.ensureHasYearMonthDay();

    result = (fYear.equals(aThat.fYear) && fMonth.equals(aThat.fMonth) && fDay.equals(aThat.fDay));

    return result;

  }

  /** 

   'Less than' comparison.

   Return <tt>true</tt> only if this <tt>DateTime</tt> comes before the given parameter, according to {@link #compareTo(DateTime)}. 

  */

  public boolean lt(DateTime aThat) {

    return compareTo(aThat) < EQUAL;

  }

  /** 

   'Less than or equal to' comparison.

   Return <tt>true</tt> only if this <tt>DateTime</tt> comes before the given parameter, according to {@link #compareTo(DateTime)},

   or this <tt>DateTime</tt> equals the given parameter. 

  */

  public boolean lteq(DateTime aThat) {

    return compareTo(aThat) < EQUAL || equals(aThat);

  }

  /**

   'Greater than' comparison. 

   Return <tt>true</tt> only if this <tt>DateTime</tt> comes after the given parameter, according to {@link #compareTo(DateTime)}.

  */

  public boolean gt(DateTime aThat) {

    return compareTo(aThat) > EQUAL;

  }

 

  /** 

   'Greater than or equal to' comparison.

   Return <tt>true</tt> only if this <tt>DateTime</tt> comes after the given parameter, according to {@link #compareTo(DateTime)},

   or this <tt>DateTime</tt> equals the given parameter. 

  */

  public boolean gteq(DateTime aThat) {

    return compareTo(aThat) > EQUAL || equals(aThat);

  }

  /** Return the smallest non-null time unit encapsulated by this <tt>DateTime</tt>. */

  public Unit getPrecision() {

    ensureParsed();

    Unit result = null;

    if (isPresent(fNanosecond)) {

      result = Unit.NANOSECONDS;

    }

    else if (isPresent(fSecond)) {

      result = Unit.SECOND;

    }

    else if (isPresent(fMinute)) {

      result = Unit.MINUTE;

    }

    else if (isPresent(fHour)) {

      result = Unit.HOUR;

    }

    else if (isPresent(fDay)) {

      result = Unit.DAY;

    }

    else if (isPresent(fMonth)) {

      result = Unit.MONTH;

    }

    else if (isPresent(fYear)) {

      result = Unit.YEAR;

    }

    return result;

  }

  /**

   Truncate this <tt>DateTime</tt> to the given precision.

   <P>The return value will have all items lower than the given precision simply set to

   <tt>null</tt>. In addition, the return value will not include any date-time String passed to the

   {@link #DateTime(String)} constructor.

  

   @param aPrecision takes any value <i>except</i> {@link Unit#NANOSECONDS} (since it makes no sense to truncate to the highest

   available precision).

   */

  public DateTime truncate(Unit aPrecision) {

    ensureParsed();

    DateTime result = null;

    if (Unit.NANOSECONDS == aPrecision) {

      throw new IllegalArgumentException("It makes no sense to truncate to nanosecond precision, since that's the highest precision available.");

    }

    else if (Unit.SECOND == aPrecision) {

      result = new DateTime(fYear, fMonth, fDay, fHour, fMinute, fSecond, null);

    }

    else if (Unit.MINUTE == aPrecision) {

      result = new DateTime(fYear, fMonth, fDay, fHour, fMinute, null, null);

    }

    else if (Unit.HOUR == aPrecision) {

      result = new DateTime(fYear, fMonth, fDay, fHour, null, null, null);

    }

    else if (Unit.DAY == aPrecision) {

      result = new DateTime(fYear, fMonth, fDay, null, null, null, null);

    }

    else if (Unit.MONTH == aPrecision) {

      result = new DateTime(fYear, fMonth, null, null, null, null, null);

    }

    else if (Unit.YEAR == aPrecision) {

      result = new DateTime(fYear, null, null, null, null, null, null);

    }

    return result;

  }

  /**

   Return <tt>true</tt> only if all of the given units are present in this <tt>DateTime</tt>.

   If a unit is <i>not</i> included in the argument list, then no test is made for its presence or absence

   in this <tt>DateTime</tt> by this method.

   */

  public boolean unitsAllPresent(Unit... aUnits) {

    boolean result = true;

    ensureParsed();

    for (Unit unit : aUnits) {

      if (Unit.NANOSECONDS == unit) {

        result = result && fNanosecond != null;

      }

      else if (Unit.SECOND == unit) {

        result = result && fSecond != null;

      }

      else if (Unit.MINUTE == unit) {

        result = result && fMinute != null;

      }

      else if (Unit.HOUR == unit) {

        result = result && fHour != null;

      }

      else if (Unit.DAY == unit) {

        result = result && fDay != null;

      }

      else if (Unit.MONTH == unit) {

        result = result && fMonth != null;

      }

      else if (Unit.YEAR == unit) {

        result = result && fYear != null;

      }

    }

    return result;

  }

  /**

   Return <tt>true</tt> only if this <tt>DateTime</tt> has a non-null values for year, month, and day.

  */

  public boolean hasYearMonthDay() {

    return unitsAllPresent(Unit.YEAR, Unit.MONTH, Unit.DAY);

  }

  /**

   Return <tt>true</tt> only if this <tt>DateTime</tt> has a non-null values for hour, minute, and second.

  */

  public boolean hasHourMinuteSecond() {

    return unitsAllPresent(Unit.HOUR, Unit.MINUTE, Unit.SECOND);

  }

  /**

   Return <tt>true</tt> only if all of the given units are absent from this <tt>DateTime</tt>.

   If a unit is <i>not</i> included in the argument list, then no test is made for its presence or absence

   in this <tt>DateTime</tt> by this method.

   */

  public boolean unitsAllAbsent(Unit... aUnits) {

    boolean result = true;

    ensureParsed();

    for (Unit unit : aUnits) {

      if (Unit.NANOSECONDS == unit) {

        result = result && fNanosecond == null;

      }

      else if (Unit.SECOND == unit) {

        result = result && fSecond == null;

      }

      else if (Unit.MINUTE == unit) {

        result = result && fMinute == null;

      }

      else if (Unit.HOUR == unit) {

        result = result && fHour == null;

      }

      else if (Unit.DAY == unit) {

        result = result && fDay == null;

      }

      else if (Unit.MONTH == unit) {

        result = result && fMonth == null;

      }

      else if (Unit.YEAR == unit) {

        result = result && fYear == null;

      }

    }

    return result;

  }

  /**

   Return this <tt>DateTime</tt> with the time portion coerced to '00:00:00.000000000'.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public DateTime getStartOfDay() {

    ensureHasYearMonthDay();

    return getStartEndDateTime(fDay, 0, 0, 0, 0);

  }

  /**

   Return this <tt>DateTime</tt> with the time portion coerced to '23:59:59.999999999'.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public DateTime getEndOfDay() {

    ensureHasYearMonthDay();

    return getStartEndDateTime(fDay, 23, 59, 59, 999999999);

  }

  /**

   Return this <tt>DateTime</tt> with the time portion coerced to '00:00:00.000000000',

   and the day coerced to 1.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public DateTime getStartOfMonth() {

    ensureHasYearMonthDay();

    return getStartEndDateTime(1, 0, 0, 0, 0);

  }

  /**

   Return this <tt>DateTime</tt> with the time portion coerced to '23:59:59.999999999',

   and the day coerced to the end of the month.

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   */

  public DateTime getEndOfMonth() {

    ensureHasYearMonthDay();

    return getStartEndDateTime(getNumDaysInMonth(), 23, 59, 59, 999999999);

  }

  /**

   Create a new <tt>DateTime</tt> by adding an interval to this one.

  

   <P>See {@link #plusDays(Integer)} as well.

  

   <P>Changes are always applied by this class <i>in order of decreasing units of time</i>:

   years first, then months, and so on. After changing both the year and month, a check on the month-day combination is made before

   any change is made to the day. If the day exceeds the number of days in the given month/year, then

   (and only then) the given {@link DayOverflow} policy applied, and the day-of-the-month is adusted accordingly.

  

   <P>Afterwards, the day is then changed in the usual way, followed by the remaining items (hour, minute, and second).

   Changes to the fractional seconds are not included in this method, since there doesn't seem to be much practical use for it.

  

   <P>The returned value cannot come after <tt>9999-12-13 23:59:59</tt>.

  

   <P>This class works with <tt>DateTime</tt>'s having the following items present :

   <ul>

   <li>year-month-day and hour-minute-second (and optional nanoseconds)

   <li>year-month-day only. In this case, if a calculation with a time part is performed, that time part

   will be initialized by this class to 00:00:00.0, and the <tt>DateTime</tt> returned by this class will include a time part.

   <li>hour-minute-second (and optional nanoseconds) only. In this case, the calculation is done starting with the  

   the arbitrary date <tt>0001-01-01</tt> (in order to remain within a valid state space of <tt>DateTime</tt>).

   </ul>

  

   @param aNumYears positive, required, in range 0...9999

   @param aNumMonths positive, required, in range 0...9999

   @param aNumDays positive, required, in range 0...9999

   @param aNumHours positive, required, in range 0...9999

   @param aNumMinutes positive, required, in range 0...9999

   @param aNumSeconds positive, required, in range 0...9999

   */

  public DateTime plus(Integer aNumYears, Integer aNumMonths, Integer aNumDays, Integer aNumHours, Integer aNumMinutes, Integer aNumSeconds, DayOverflow aDayOverflow) {

    DateTimeInterval interval = new DateTimeInterval(this, aDayOverflow);

    return interval.plus(aNumYears, aNumMonths, aNumDays, aNumHours, aNumMinutes, aNumSeconds);

  }

  /**

   Create a new <tt>DateTime</tt> by subtracting an interval to this one.

  

   <P>See {@link #minusDays(Integer)} as well.

   <P>This method has nearly the same behavior as {@link #plus(Integer, Integer, Integer, Integer, Integer, Integer, DayOverflow)},

   except that the return value cannot come before <tt>0001-01-01 00:00:00</tt>.

   */

  public DateTime minus(Integer aNumYears, Integer aNumMonths, Integer aNumDays, Integer aNumHours, Integer aNumMinutes, Integer aNumSeconds, DayOverflow aDayOverflow) {

    DateTimeInterval interval = new DateTimeInterval(this, aDayOverflow);

    return interval.minus(aNumYears, aNumMonths, aNumDays, aNumHours, aNumMinutes, aNumSeconds);

  }

  /**

   Return a new <tt>DateTime</tt> by adding an integral number of days to this one.

  

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   @param aNumDays can be either sign; if negative, then the days are subtracted.

   */

  public DateTime plusDays(Integer aNumDays) {

    ensureHasYearMonthDay();

    int thisJDAtNoon = getModifiedJulianDayNumber() + 1 + EPOCH_MODIFIED_JD;

    int resultJD = thisJDAtNoon + aNumDays;

    DateTime datePortion = fromJulianDayNumberAtNoon(resultJD);

    return new DateTime(datePortion.getYear(), datePortion.getMonth(), datePortion.getDay(), fHour, fMinute, fSecond, fNanosecond);

  }

  /**

   Return a new <tt>DateTime</tt> by subtracting an integral number of days from this one.

  

   <P>Requires year-month-day to be present; if not, a runtime exception is thrown.

   @param aNumDays can be either sign; if negative, then the days are added.

   */

  public DateTime minusDays(Integer aNumDays) {

    return plusDays(-1 * aNumDays);

  }

  /** 

   The whole number of days between this <tt>DateTime</tt> and the given parameter.

   <P>Requires year-month-day to be present, both for this <tt>DateTime</tt> and for the <tt>aThat</tt>

   parameter; if not, a runtime exception is thrown.

  */

  public int numDaysFrom(DateTime aThat) {

    return aThat.getModifiedJulianDayNumber() - this.getModifiedJulianDayNumber();

  }

  /**

    The number of seconds between this <tt>DateTime</tt> and the given argument.

    <P>If only time information is present in both this <tt>DateTime</tt> and <tt>aThat</tt>, then there are

    no restrictions on the values of the time units.

    <P>If any date information is present, in either this <tt>DateTime</tt> or <tt>aThat</tt>,

    then full year-month-day must be present in both; if not, then the date portion will be ignored, and only the

    time portion will contribute to the calculation.

  */

  public long numSecondsFrom(DateTime aThat) {

    long result = 0;

    if(hasYearMonthDay() && aThat.hasYearMonthDay()){

      result = numDaysFrom(aThat) * 86400; //just the day portion

    }

    result = result - this.numSecondsInTimePortion() + aThat.numSecondsInTimePortion();

    return result;

  }

  /**

   Validate that the given String can be used by this class to format a <tt>DateTime</tt>.

  

   <P>Some format strings can be used only with a <tt>Locale</tt>.

   Internally, this method uses <tt>Locale.ENGLISH</tt> as a representative test <tt>Locale</tt>.

  */

  public static boolean isValidFormatString(String aFormatString) {

    boolean result = false;

    DateTime dt = new DateTime(1972, 11, 11, 15, 30, 59, 999999999);

    try {

      String text = dt.format(aFormatString, Locale.ENGLISH);

      result = true;

    }

    catch (RuntimeException ex) {

      //do nothing - not valid string

    }

    return result;

  }

  /**

   Output this <tt>DateTime</tt> as a formatted String using numbers, with no localizable text.

  

   <P>Example:

   <PRE>dt.format("YYYY-MM-DD hh:mm:ss");</PRE>

   would generate text of the form

   <PRE>2009-09-09 18:23:59</PRE>

  

   <P>If months, weekdays, or AM/PM indicators are output as localizable text, you must use {@link #format(String, Locale)}.

   @param aFormat uses the <a href="#FormattingLanguage">formatting mini-language</a> defined in the class comment.

   */

  public String format(String aFormat) {

    DateTimeFormatter format = new DateTimeFormatter(aFormat);

    return format.format(this);

  }

  /**

   Output this <tt>DateTime</tt> as a formatted String using numbers and/or localizable text.

  

   <P>This method is intended for alphanumeric output, such as '<tt>Sunday, November 14, 1858 10:00 AM</tt>'.

   <P>If months and weekdays are output as numbers, you are encouraged to use {@link #format(String)} instead.

  

   @param aFormat uses the <a href="#FormattingLanguage">formatting mini-language</a> defined in the class comment.

   @param aLocale used to generate text for Month, Weekday and AM/PM indicator; required only by patterns which return localized

   text, instead of numeric forms.

   */

  public String format(String aFormat, Locale aLocale) {

    DateTimeFormatter format = new DateTimeFormatter(aFormat, aLocale);

    return format.format(this);

  }

  /**

   Output this <tt>DateTime</tt> as a formatted String using numbers and explicit text for months, weekdays, and AM/PM indicator.

   <P>Use of this method is likely relatively rare; it should be used only if the output of {@link #format(String, Locale)}  is

   inadequate.

  

   @param aFormat uses the <a href="#FormattingLanguage">formatting mini-language</a> defined in the class comment.

   @param aMonths contains text for all 12 months, starting with January; size must be 12.

   @param aWeekdays contains text for all 7 weekdays, starting with Sunday; size must be 7.

   @param aAmPmIndicators contains text for A.M and P.M. indicators (in that order); size must be 2.

   */

  public String format(String aFormat, List<String> aMonths, List<String> aWeekdays, List<String> aAmPmIndicators) {

    DateTimeFormatter format = new DateTimeFormatter(aFormat, aMonths, aWeekdays, aAmPmIndicators);

    return format.format(this);

  }

  /**

   Return the current date-time.

   <P>Combines the configured implementation of {@link TimeSource} with the given {@link TimeZone}.

   The <tt>TimeZone</tt> will typically come from your implementation of {@link TimeZoneSource}.

  

   <P>In an Action, the current date-time date can be referenced using

   <PRE>DateTime.now(getTimeZone())</PRE>

   See {@link ActionImpl#getTimeZone()}.

  

   <P>Only millisecond precision is possible for this method.

   */

  public static DateTime now(TimeZone aTimeZone) {

    TimeSource timesource = BuildImpl.forTimeSource();

    return forInstant(timesource.currentTimeMillis(), aTimeZone);

  }

  /**

   Return the current date.

   <P>As in {@link #now(TimeZone)}, but truncates the time portion, leaving only year-month-day.

   <P>In an Action, today's date can be referenced using

   <PRE>DateTime.today(getTimeZone())</PRE>

   See {@link ActionImpl#getTimeZone()}.

   */

  public static DateTime today(TimeZone aTimeZone) {

    DateTime result = now(aTimeZone);

    return result.truncate(Unit.DAY);

  }

  /** Return <tt>true</tt> only if this date is in the future, with respect to {@link #now(TimeZone)}. */

  public boolean isInTheFuture(TimeZone aTimeZone) {

    return now(aTimeZone).lt(this);

  }

  /** Return <tt>true</tt> only if this date is in the past, with respect to {@link #now(TimeZone)}. */

  public boolean isInThePast(TimeZone aTimeZone) {

    return now(aTimeZone).gt(this);

  }

 

  /**

    Return a <tt>DateTime</tt> corresponding to a change from one {@link TimeZone} to another.

   

    <P>A <tt>DateTime</tt> object has an implicit and immutable time zone.

    If you need to change the implicit time zone, you can use this method to do so.

   

    <P>Example :

    <PRE>

TimeZone toIndonesia = TimeZone.getTimeZone("Asia/Jakarta");

DateTime newDt = oldDt.changeTimeZone(fromUK, toIndonesia);

    </PRE>

    

   <P>Requires year-month-day-hour to be present; if not, a runtime exception is thrown.

   @param aFromTimeZone the implicit time zone of this object.

   @param aToTimeZone the implicit time zone of the <tt>DateTime</tt> returned by this method.

   @return aDateTime corresponding to the change of time zone implied by the 2 parameters.

   */

  public DateTime changeTimeZone(TimeZone aFromTimeZone, TimeZone aToTimeZone){

    DateTime result = null;

    ensureHasYearMonthDay();

    if (unitsAllAbsent(Unit.HOUR)){

      throw new IllegalArgumentException("DateTime does not include the hour. Cannot change the time zone if no hour is present.");

    }

    Calendar fromDate = new GregorianCalendar(aFromTimeZone);

    fromDate.set(Calendar.YEAR, getYear());

    fromDate.set(Calendar.MONTH, getMonth()-1);

    fromDate.set(Calendar.DAY_OF_MONTH, getDay());

    fromDate.set(Calendar.HOUR_OF_DAY, getHour());

    if(getMinute() != null) {

      fromDate.set(Calendar.MINUTE, getMinute());

    }

    else {

      fromDate.set(Calendar.MINUTE, 0);

    }

    //other items zeroed out here, since they don't matter for time zone calculations

    fromDate.set(Calendar.SECOND, 0);

    fromDate.set(Calendar.MILLISECOND, 0);

    //millisecond precision is OK here, since the seconds/nanoseconds are not part of the calc

    Calendar toDate = new GregorianCalendar(aToTimeZone);

    toDate.setTimeInMillis(fromDate.getTimeInMillis());

    //needed if this date has hour, but no minute (bit of an oddball case) :

    Integer minute = getMinute() != null ? toDate.get(Calendar.MINUTE) : null;

    result = new DateTime(

      toDate.get(Calendar.YEAR), toDate.get(Calendar.MONTH) + 1, toDate.get(Calendar.DAY_OF_MONTH),

      toDate.get(Calendar.HOUR_OF_DAY), minute, getSecond(), getNanoseconds()

    );

    return result;

  }

  /**

   Compare this object to another, for ordering purposes.

   <P> Uses the 7 date-time elements (year..nanosecond). The Year is considered the most

   significant item, and the Nanosecond the least significant item. Null items are placed first in this comparison.

   */

  public int compareTo(DateTime aThat) {

    if (this == aThat) return EQUAL;

    ensureParsed();

    aThat.ensureParsed();

    NullsGo nullsGo = NullsGo.FIRST;

    int comparison = ModelUtil.comparePossiblyNull(this.fYear, aThat.fYear, nullsGo);

    if (comparison != EQUAL)  return comparison;

    comparison = ModelUtil.comparePossiblyNull(this.fMonth, aThat.fMonth, nullsGo);

    if (comparison != EQUAL)  return comparison;

    comparison = ModelUtil.comparePossiblyNull(this.fDay, aThat.fDay, nullsGo);

    if (comparison != EQUAL)  return comparison;

    comparison = ModelUtil.comparePossiblyNull(this.fHour, aThat.fHour, nullsGo);

    if (comparison != EQUAL)  return comparison;

    comparison = ModelUtil.comparePossiblyNull(this.fMinute, aThat.fMinute, nullsGo);

    if (comparison != EQUAL)  return comparison;

    comparison = ModelUtil.comparePossiblyNull(this.fSecond, aThat.fSecond, nullsGo);

    if (comparison != EQUAL)  return comparison;

    comparison = ModelUtil.comparePossiblyNull(this.fNanosecond, aThat.fNanosecond, nullsGo);

    if (comparison != EQUAL)  return comparison;

    return EQUAL;

  }

  /**

   Equals method for this object.

  

   <P>Equality is determined by the 7 date-time elements (year..nanosecond).

   */

  @Override public boolean equals(Object aThat) {

    /*

     * Implementation note: it was considered branching this method, according to whether

     * the objects are already parsed. That was rejected, since maintaining 'synchronicity'

     * with hashCode would not then be possible, since hashCode is based only on one object,

     * not two.

     */

    ensureParsed();

    Boolean result = ModelUtil.quickEquals(this, aThat);

    if (result == null) {

      DateTime that = (DateTime)aThat;

      that.ensureParsed();

      result = ModelUtil.equalsFor(this.getSignificantFields(), that.getSignificantFields());

    }

    return result;

  }

  /**

   Hash code for this object.

  

   <P> Uses the same 7 date-time elements (year..nanosecond) as used by

   {@link #equals(Object)}.

   */

  @Override public int hashCode() {

    if (fHashCode == 0) {

      ensureParsed();

      fHashCode = ModelUtil.hashCodeFor(getSignificantFields());

    }

    return fHashCode;

  }

  /**

   Intended for debugging only.

  

   <P>To format this <tt>DateTime</tt> for presentation to the user, see the various <tt>format</tt> methods.

   <P> If the {@link #DateTime(String)} constructor was called, then return that String. Otherwise,

   the return value is constructed from each date-time element.

  

   <P>In the latter case, the format of the returned String is verbose, and displays all date-time elements,

   including <tt>null</tt> items. Some will be displeased with the format of such <tt>String</tt>s; the

   intent of returning a verbose, rather unfriendly format is to avoid having programmers inadvertently call

   <tt>toString</tt> when they should really be calling one of the <tt>format</tt> methods.

   */

  @Override public String toString() {

    String result = "";

    if (Util.textHasContent(fDateTime)) {

      result = fDateTime;

    }

    else {

      StringBuilder builder = new StringBuilder();

      addToString("Y", fYear, builder);

      addToString("M", fMonth, builder);

      addToString("D", fDay, builder);

      addToString("h", fHour, builder);

      addToString("m", fMinute, builder);

      addToString("s", fSecond, builder);

      addToString("f", fNanosecond, builder);

      result = builder.toString().trim();

    }

    return result;

  }

  // PACKAGE-PRIVATE (for unit testing, mostly)

    ItemOutOfRange(String aMessage) {

      super(aMessage);

    }

  }

  static final class MissingItem extends RuntimeException {

    MissingItem(String aMessage) {

      super(aMessage);

    }

  }

  /** Intended as internal tool, for testing only. Not scope is not public! */

  void ensureParsed() {

    if (!fIsAlreadyParsed) {

      parseDateTimeText();

    }

  }

  /**

   Return the number of days in the given month. The returned value depends on the year as

   well, because of leap years. Returns <tt>null</tt> if either year or month are

   absent. WRONG - should be public??

   Package-private, needed for interval calcs.

   */

  static Integer getNumDaysInMonth(Integer aYear, Integer aMonth) {

    Integer result = null;

    if (aYear != null && aMonth != null) {

      if (aMonth == 1) {

        result = 31;

      }

      else if (aMonth == 2) {

        result = isLeapYear(aYear) ? 29 : 28;

      }

      else if (aMonth == 3) {

        result = 31;

      }

      else if (aMonth == 4) {

        result = 30;

      }

      else if (aMonth == 5) {

        result = 31;

      }

      else if (aMonth == 6) {

        result = 30;

      }

      else if (aMonth == 7) {

        result = 31;

      }

      else if (aMonth == 8) {

        result = 31;

      }

      else if (aMonth == 9) {

        result = 30;

      }

      else if (aMonth == 10) {

        result = 31;

      }

      else if (aMonth == 11) {

        result = 30;