This question already has an answer here:
- Timezone conversion 11 answers
I am trying to obtain a simple conversion from one time zone into another using Java Date and Calendar. I am trying to run the following code
Calendar instance = Calendar.getInstance(TimeZone.getTimeZone("Europe/London"));
Date date = instance.getTime();
System.out.println(date);
GregorianCalendar instance2 = new GregorianCalendar(TimeZone.getTimeZone("Europe/Athens"));
instance2.setTime(instance.getTime());
System.out.println(instance2.getTime());
but that still returns the same date, rather than +1 hour... The whole problem seems trivial but i cannot find any simple answer to this. Thanks in advance for your help.
When you print the date using
System.out.println(date); or System.out.println(instance2.getTime());
, theDate
returned byinstance2.getTime()
isTimeZone independent
and always prints the date in local timezone.Instead you may want to use
DateFormat/SimpleDateFormat
:The accepted answer is correct. The java.util.Date class has no time zone assigned†, yet it's
toString
implementation confusingly applies the JVM's current default time zone.Avoid java.util.Date & .Calendar
This is one of many reasons to avoid the notoriously troublesome java.util.Date, .Calendar, and SimpleDateFormat classes bundled with Java. Avoid them. Instead use either:
Joda-Time
Some example code in Joda-Time 2.3 follows. Search StackOveflow for many more examples and much discussion.
java.time
Java 8 and later has a new java.time package built-in. This package was inspired by Joda-Time. While they share some similarities and class names, they are different; each has features the other lacks. One notable difference is that java.time avoids constructors, instead uses static instantiation methods.
In the case of this Question, they work in the same fashion. Specify a time zone, and call a
now
method to get current moment, then create a new instance based on the old immutable instance to adjust for time zone.Note the two different time zone classes. One is a named time zone including all the rules for Daylight Saving Time and other such anomalies plus an offset from UTC while the other is only the offset.
†Actually the
java.util.Date
class does have a time zone buried within its source code. But the class ignores that time zone for most practical purposes. So, as shorthand, it’s often said that j.u.Date has no time zone assigned. Confusing? Yes. Avoid the mess that is j.u.Date and go with Joda-Time and/or java.time.You can use the following code snippet