[
https://issues.apache.org/jira/browse/OLINGO-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052182#comment-14052182
]
Michael Bolz commented on OLINGO-329:
-------------------------------------
Hello Rudy,
how important is a fix (or clarification) of this issue for you?
My question is because we want to do a release {{2.0.0}} and this is the only
open issue which prevents it.
Would it be ok to move a solution to next version ({{2.1.0}})?
Kind regards,
Michael
[~chandan.v.a]: Or would it be possible to enhance/fix this the next few days?
Perhaps I can also take a look into it ;o)
> Not all JPA data types handled correctly
> ----------------------------------------
>
> Key: OLINGO-329
> URL: https://issues.apache.org/jira/browse/OLINGO-329
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Affects Versions: V2 1.2.0
> Reporter: Rudy Gardelein
> Assignee: Chandan V.A
> Fix For: V2 2.0.0
>
>
> As described in the following link
> (http://scn.sap.com/community/gateway/blog/2014/02/05/odata-producer-using-apache-olingo-with-mysql-jpa-tomcat-web-server)
> there are issues with the correct translation of JPA data types boolean and
> timestamp in version V2 1.2 of Olingo.
> Boolean datatype is translated to Java byte type. Timestamp is translated to
> Java timestamp. Both of these however do not work in the Odata service as
> generated by Olingo.
> Raising this issue as suggested by Chandan V.A. from SAP.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
