If I take the overlap (using the Interval.overlap function, each value were displayed using toString) between 2004-10-31T00:00:00.000/2005-10-31T00:00:00.000 (ISOChronology[UTC]) and 2005-06-04T00:00:00.000/2006-06-30T00:00:00.000 (ISOChronology[UTC]) then the result is 2005-06-04T02:00:00.000/2005-10-31T01:00:00.000 (ISOChronology[Europe/Prague])
Notice the time part is different then both originals! Maybe I don't understand something but this doesn't seem to be a correct result. The problem is obviously related to the timezones, the overlap function creates a new Interval, but using a constructor with null chronology which is not the same as the chronology used in the original intervals. Another, maybe related thing what I don't understand: Now if I convert the start of the resulting interval using toMutableDateTime and start to add one day (using addDays(1)) several times then eventually (at the end of summer time) the result is: 2005-10-30T02:00:00.000+01:00 This is T01H UTC and I started with T0Z so this really seems to be factually wrong. I assume that is I add one day (not 24 hours!) then the time part of a datetime mustn't change even at the daylight savings boundary. Am I wrong? Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Joda-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/joda-interest
