You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/08/02 05:13:00 UTC

[jira] [Updated] (SLING-11546) ValueMap.get("calendar", String.class) conversion loses timezone information

     [ https://issues.apache.org/jira/browse/SLING-11546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated SLING-11546:
-------------------------------------
    Affects Version/s:     (was: Resource Resolver 1.6.16)

> 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
>    Affects Versions: API 2.21.0
>            Reporter: Jelle Bouwmans
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: API 2.27.4
>
>         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)