[
https://issues.apache.org/jira/browse/OLINGO-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077498#comment-14077498
]
Chandan V.A commented on OLINGO-380:
------------------------------------
Hello Emmanuel, Hello [~rrainey_sap]
Please refer to issue - OLINGO-293. A similar request was raised to support
java.util.Date data type. Since most of the constructors in java.util.Date is
deprecated from JDK1.1 on wards a conscious decision was taken not to support
java.util.Date.
Now I see lot of queries arising around usage of java.util.Date, I have
implemented the same in the version 2.0.1-SNAPSHOT. I also noticed that there
is a bug where create/update on java.sql.Date, java.sql.Time was not handled. I
have fixed that issue as well.
http://git-wip-us.apache.org/repos/asf/olingo-odata2/commit/44604c78
Thanks
Kind Regards
Chandan
> Cannot use Date attribute with Jpa
> ----------------------------------
>
> Key: OLINGO-380
> URL: https://issues.apache.org/jira/browse/OLINGO-380
> Project: Olingo
> Issue Type: Bug
> Components: odata2-jpa
> Affects Versions: V2 2.0.0
> Reporter: Emmanuel Potvin
> Assignee: Chandan V.A
>
> Line 85 :
> } else if ((jpaType.equals(Date.class)) ||
> (jpaType.equals(Calendar.class)) ||
> jpaType.equals(Timestamp.class)) {
> try {
> The Date.class used is java.sql.Date. I suppose it should be java.util.Date.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
