[
https://issues.apache.org/jira/browse/SLING-11546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581767#comment-17581767
]
Henry Kuijpers commented on SLING-11546:
----------------------------------------
It looks like
{code}
return
ZonedDateTime.ofInstant(Instant.ofEpochMilli(calendar.getTimeInMillis()),
calendar.getTimeZone().toZoneId()).format(DateTimeFormatter.ISO_OFFSET_DATE_TIME);
{code}
does give the expected results (taking into account the timezone).
However, are there situations where the timezone will not be available?
> ValueMap.get("calendar", String.class) conversion loses timezone information
> ----------------------------------------------------------------------------
>
> Key: SLING-11546
> URL: https://issues.apache.org/jira/browse/SLING-11546
> Project: Sling
> Issue Type: Bug
> Components: API, ResourceResolver
> Affects Versions: API 2.21.0, Resource Resolver 1.6.16
> Reporter: Jelle Bouwmans
> Priority: Major
> Attachments: image-2022-08-19-10-41-27-129.png,
> image-2022-08-19-10-45-25-409.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When doing a ValueMap.get("calendar", String.class) conversion, before
> SLING-8116,
> ISO8601.format() was used. Now, Calendar.toInstant().toString() is used. This
> gives a different result, because the ISO8601 gives the correct timezone, but
> toInstant() gives the Zulu time.
> toInstant() does the following:
> {quote}public final Instant toInstant() \{ return
> Instant.ofEpochMilli(getTimeInMillis()); }
> {quote}
> Timezones and offsets are completely ignored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
