[
https://issues.apache.org/jira/browse/OLINGO-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-961.
------------------------------------
Resolution: Not A Bug
Assignee: Christian Amend
Hi the functionallity is there. The calendar class is the default as described
in the JavaDoc of the EdmSimpleType. If another Java type is needed use the
EntityProviderReadProperties to specify the Timestamp class as a return type
for a property.
> Higher precision support for DateTimeOffset
> --------------------------------------------
>
> Key: OLINGO-961
> URL: https://issues.apache.org/jira/browse/OLINGO-961
> Project: Olingo
> Issue Type: Bug
> Affects Versions: V2 2.0.7
> Reporter: Sagar
> Assignee: Christian Amend
>
> I am getting '2016-05-23T11:51:00.8398830Z' string from SAP OData endpoint
> for the Edm.DateTimeOffset data type field.
> I believe that this is valid format as per the
> http://www.odata.org/documentation/odata-version-2-0/overview/ (# 6.
> Primitive Data Types).
> Looks like the apache olingo 2.0.7 version is not able to parse this valid
> DateTimeOffset String.
> Isn't '2016-05-23T11:51:00.8398830Z' is valid format for Edm.DateTimeOffset
> data type?
> For more details refer my last 2 comments on
> https://issues.apache.org/jira/browse/OLINGO-749
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
