[
https://issues.apache.org/jira/browse/OLINGO-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrian Görler updated OLINGO-1408:
----------------------------------
Attachment: OLINGO-1408.patch
> OData V4: Java 8 DateTime API support by Olingo
> -----------------------------------------------
>
> Key: OLINGO-1408
> URL: https://issues.apache.org/jira/browse/OLINGO-1408
> Project: Olingo
> Issue Type: New Feature
> Components: odata4-commons
> Reporter: Adrian Görler
> Priority: Major
> Attachments: OLINGO-1408.patch
>
>
> *Support types of new Date/Time API*
>
> The types of the new Date/Time API can now be used as property values.
>
> The following mappings are now supported
>
> *EdmDateTimeOffset*
> * java.time.Instant
> * java.time.ZonedDateTime
> * java.util.Calendar
> * java.util.Date
> * java.sql.Timestamp
> * java.lang.Long
>
> *EdmDate*
> * java.time.LocalDate
> * java.sql.Date
> *EdmTimeOfDay*
> * java.time.LocalTime
> * java.sql.Time
> Only these mappings capture the semantics correctly.
>
> For legacy reasons also supported are the following mappings are still
> supported:
>
> *EdmDate*
> * java.util.Calendar (date component in the TZ of the calendar)
> * java.util.Date (date component in UTC)
> * java.sql.Timestamp (date component in UTC)
> * java.lang.Long (date component in UTC)
> *EdmTimeOfDay*
> * java.util.Calendar (time component in the TZ of the calendar)
> * java.util.Date (time component in UTC)
> * java.sql.Timestamp (time component in UTC)
> * java.lang.Long (time component in UTC)
> For legacy reasons the default mapping types are unchanged (and remain
> semantically incorrect):
> EdmDate -> java.util.Calendar, java.util.Date,
> java.sql.Timestamp
> EdmTimeOfDay -> java.util.Calendar, java.util.Date,
> java.sql.Timestamp
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
