You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Rudy Gardelein (JIRA)" <ji...@apache.org> on 2014/06/24 11:25:24 UTC
[jira] [Created] (OLINGO-329) Not all JPA data types handled
correctly
Rudy Gardelein created OLINGO-329:
-------------------------------------
Summary: 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
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)