Hontvari Jozsef wrote: >I thought that the Instant class could be great on the server side, >because the chronology used is always ISO in the UTC time zone. On the >other hand all of its toDateTime etc. methods are convert to the >*default* time zone, not to UTC. The default time zone is quite useless >on the server-side if it is in an international environment (nobody is >interested in where the server is...). So I feel it would be more >consistent if it converts to UTC dates. As an alternative, a new >toDateTimeUTC() function could be added, although the two current >similar functions (which do the same) are already confusing enough :) > > Instant is really meant to represent just a millisecond instant without a chronology or zone at all. Its only actually in ISO+UTC due to poor implementation.
As such, when converting to a DateTime, the toDateTime method does the default behaviour when converting from no time zone, and uses the default zone. If you truly want to run your server with no knowledge of zones, you could change the default time zone: DateTimeZone.setDefault(DateTimeZone.UTC); Stephen 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
