nmiguezg opened a new pull request, #54: URL: https://github.com/apache/olingo-odata2/pull/54
When the client library reads a query payload in Atom format containing values of type EdmDateTime or EdmDateTimeOffset with a precision greater than milliseconds, it throws an EdmSimpleTimeException, causing the entire query to fail. According to the OData 2.0 standard specification ([OData 2.0 Overview](https://www.odata.org/documentation/odata-version-2-0/overview/#AbstractTypeSystem), _6. Primitive Data Types_ section), literals of type EdmDateTime and EdmDateTimeOffset support up to seven decimal places of precision: > datetime'yyyy-mm-ddThh:mm[:ss[.fffffff]]' NOTE: Spaces are not allowed between datetime and quoted portion. datetime is case-insensitive > datetimeoffset'<dateTimeOffsetLiteral>' dateTimeOffsetLiteral = Defined by the lexical representation for datetime (including timezone offset) at https://www.w3.org/TR/xmlschema-2 So, here it is fixed by changing both date types default type from `java.util.Calendar` to `java.sql.Timestamp` (as it's also the default type in the olingo-odata4 library). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@olingo.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
