[
https://issues.apache.org/jira/browse/OLINGO-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manon van Tilburg updated OLINGO-1646:
--------------------------------------
Description:
Depending on the mapped Java class that is set for {{EdmDate}} and
{{{}EdmDateTimeOffset{}}}, conversion of (historical) dates can give unexpected
results:
# Dates before the Julian-Gregorian cutover date (by default October 15, 1582
(Gregorian)) are treated as Julian when {{java.util.Calendar}} is (indirectly)
used. When using {{java.time}} types, these dates are treated as (proleptic)
Gregorian instead
# The mapped Java class is not always used correctly
See [pull request|https://github.com/apache/olingo-odata4/pull/173] for fix and
related unit tests
was:
Depending on the mapped Java class that is set for {{EdmDate}} and
{{{}EdmDateTimeOffset{}}}, conversion of (historical) dates can give unexpected
results:
# Dates before the Julian-Gregorian cutover date (by default October 15, 1582
(Gregorian)) are treated as Julian when {{java.util.Calendar}} is (indirectly)
used. When using {{java.time}} types, these dates are treated as (proleptic)
Gregorian instead
# The mapped Java class is not always used correctly
> Invalid date/time conversions
> -----------------------------
>
> Key: OLINGO-1646
> URL: https://issues.apache.org/jira/browse/OLINGO-1646
> Project: Olingo
> Issue Type: Bug
> Reporter: Manon van Tilburg
> Priority: Major
>
> Depending on the mapped Java class that is set for {{EdmDate}} and
> {{{}EdmDateTimeOffset{}}}, conversion of (historical) dates can give
> unexpected results:
> # Dates before the Julian-Gregorian cutover date (by default October 15,
> 1582 (Gregorian)) are treated as Julian when {{java.util.Calendar}} is
> (indirectly) used. When using {{java.time}} types, these dates are treated as
> (proleptic) Gregorian instead
> # The mapped Java class is not always used correctly
>
> See [pull request|https://github.com/apache/olingo-odata4/pull/173] for fix
> and related unit tests
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
