[
https://issues.apache.org/jira/browse/OLINGO-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296303#comment-15296303
]
Sagar commented on OLINGO-749:
------------------------------
Hi Chris,
I believe that https://issues.apache.org/jira/browse/OLINGO-749 is fixed and
source code is available in github.
I wanted a fix for this issue, therefore I have taken a latest code github
(https://github.com/apache/olingo-odata2) and did a local maven build.
I am using the locally built libraries olingo-odata2-core-2.0.7-SNAPSHOT.jar
and olingo-odata2-api-2.0.7-SNAPSHOT.jar
While using this latest 2.0.7 libraries I am getting below error while working
with Edm.DateTimeOffset object.
'The literal '2016-05-23T11:51:00.8398830Z' is not formatted properly
Find the attached screenshot where the exception is thrown. I am not familiar
with this code
(odata2-lib\odata-core\src\main\java\org\apache\olingo\odata2\core\edm\EdmDateTimeOffset.java
line #118).
Following condition is getting true, hence I am getting
org.apache.olingo.odata2.api.ep.EntityProviderException: An exception of type
'EdmSimpleTypeException' occurred.
if (nanoSeconds % (1000 * 1000) != 0 &&
!returnType.isAssignableFrom(Timestamp.class))
during my debugging values were nanoSeconds = 938873000 and returnType is of
type java.util.Calendar.
Can you please have look at this issue and let us know if this is defect or not?
Thanks,
Sagar
> Support Higher precision for TimeStamps
> ---------------------------------------
>
> Key: OLINGO-749
> URL: https://issues.apache.org/jira/browse/OLINGO-749
> Project: Olingo
> Issue Type: Improvement
> Components: odata2-core
> Affects Versions: V2 2.0.2, V2 2.0.3, V2 2.0.4, V2 2.0.5, V2 2.0.6
> Environment: OData Provisioning, Consumption
> Reporter: Sachin
> Assignee: Christian Amend
> Fix For: V2 2.0.7, V2 2.1.0
>
>
> Hi,
> Currently in Olingo, a precision of 3 is supported at the most for
> Edm.Time,DateTime. This limitation needs to be addressed as there are OData
> V2 services which has values with higher precision. This affects both
> provisioning and consumption scenarios.
> Thanks,
> Sachin
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
