[
https://issues.apache.org/jira/browse/OLINGO-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238054#comment-17238054
]
Ramya Vasanth commented on OLINGO-1496:
---------------------------------------
This is fixed as part of commitÂ
https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=d310611c33aa2d3781b785d1e758efd44f3275e5
> ODataV2: Fix handling of Timestamp values in serialization
> ----------------------------------------------------------
>
> Key: OLINGO-1496
> URL: https://issues.apache.org/jira/browse/OLINGO-1496
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Reporter: Ramya Vasanth
> Priority: Major
>
> This change fixes a bug in the response serialization in case a Timestamp
> value was provided. In this case the wrong offset was determined. The change
> removes the offset handling completely because it is actually sufficient to
> write the response in UTC time zone.
> Further more the precision restriction for JSON responses was removed. In
> case there is a higher precision, it is simply truncated. This allows for
> example to write an etag value with a micro second precision for a json
> formatted response.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
