tl;dr
LocalDateTime.parse( "2016-09-27T19:35:32.717" ).atZone( ZoneOffset.UTC )
Details
Your input string is not a UTC value: 2016-09-27T19:35:32.717
. That String lacks any information about offset-from-UTC or time zone.
You are using troublesome old date-time classes, now legacy, supplanted by the java.time classes.
LocalDateTime
Parse that string as a LocalDateTime
object lacking any offset or time zone.
That input string happens to comply with the ISO 8601 standard for date-time strings. The java.time classes use ISO 8601 formats by default when parsing/generating strings. So no need to specify a formatting pattern.
LocalDateTime ldt = LocalDateTime.parse( "2016-09-27T19:35:32.717" );
OffsetDateTime
If by context you know for certain that string was meant to represent a moment in UTC, then apply an offset to get a OffsetDateTime
. Use the predefined constant ZoneOffset.UTC
.
OffsetDateTime odt = ldt.atZone( ZoneOffset.UTC );
From there you can use DateTimeFormatter
to generate Strings in various formats, if needed.
ZonedDateTime
If you want to view that same moment through the lens of some particular region’s time zone, apply a ZoneId
to get a ZonedDateTime
.
A time zone is an offset-from-UTC plus a set of rules for handling anomalies such as Daylight Saving Time (DST).
Specify a proper time zone name in the format of continent/region
. Never use the 3-4 letter abbreviation such as EST
or IST
as they are not true time zones, not standardized, and not even unique(!).
ZoneId z = ZoneId.of( "America/Montreal" );
ZonedDateTime zdt = odt.atZoneSameInstant( z );
You can get the user’s current default time zone if desired. But be aware this default can change at any moment, even during runtime. So if important, you should ask the user for intended/desired time zone rather than assume.
ZoneId z = ZoneId.systemDefault();
About java.time
The java.time framework is built into Java 8 and later. These classes supplant the troublesome old legacy date-time classes such as java.util.Date
, .Calendar
, & java.text.SimpleDateFormat
.
The Joda-Time project, now in maintenance mode, advises migration to java.time.
To learn more, see the Oracle Tutorial. And search Stack Overflow for many examples and explanations. Specification is JSR 310.
Where to obtain the java.time classes?
- Java SE 8 and SE 9 and later
- Built-in.
- Part of the standard Java API with a bundled implementation.
- Java 9 adds some minor features and fixes.
- Java SE 6 and SE 7
- Much of the java.time functionality is back-ported to Java 6 & 7 in ThreeTen-Backport.
- Android
The ThreeTen-Extra project extends java.time with additional classes. This project is a proving ground for possible future additions to java.time. You may find some useful classes here such as Interval
, YearWeek
, YearQuarter
, and more.