[
https://issues.apache.org/jira/browse/OLINGO-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979072#comment-14979072
]
Ramesh Reddy commented on OLINGO-793:
-------------------------------------
Christian, I can settle for configuration option ;)
The OData spec specifies the "variable" keyword for "scale" to avoid this, but
defaults to 0, and for precision also it defaults to 0. What is lacking from
the links Ralf provided above is they do not define the behavior/restrictions
when they are specified as defaults. I would have hoped the OData spec
defaulted to "variable" in both situations to avoid the strict interpretation
by frameworks.
> Precision on EdmDateTimeOffset should be optional
> -------------------------------------------------
>
> Key: OLINGO-793
> URL: https://issues.apache.org/jira/browse/OLINGO-793
> Project: Olingo
> Issue Type: Bug
> Components: odata4-commons
> Affects Versions: (Java) V4 4.0.0
> Reporter: Ramesh Reddy
>
> According to [1] the precision attribute on EdmdateTimeOffset is optional
> facet that can be defined. However the code [2] fails with
> IllegalArgumentException is it found to be null.
> [1]
> http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part3-csdl/odata-v4.0-errata02-os-part3-csdl-complete.html#_Toc406397957
> [2]
> https://github.com/apache/olingo-odata4/blob/master/lib/commons-core/src/main/java/org/apache/olingo/commons/core/edm/primitivetype/EdmDateTimeOffset.java#L253
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
