[
https://issues.apache.org/jira/browse/ISIS-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297379#comment-14297379
]
ASF subversion and git services commented on ISIS-1015:
-------------------------------------------------------
Commit 27dcb7634e512fb3283239fd477430040b18fb69 in isis's branch
refs/heads/master from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=27dcb76 ]
ISIS-1012 ISIS-1015 Update the TODO
> DataNucleus doesn't support LocalDateTime
> -----------------------------------------
>
> Key: ISIS-1015
> URL: https://issues.apache.org/jira/browse/ISIS-1015
> Project: Isis
> Issue Type: Sub-task
> Components: Core: Objectstore: JDO
> Affects Versions: core-1.8.0
> Reporter: Martin Grigorov
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: core-2.0.0
>
>
> While debugging ISIS-1012 I've found that Kitchensink app doesn't behave
> correctly for Joda-Time's LocalDateTime:
> org.apache.isis.viewer.wicket.ui.components.scalars.jodatime.JodaLocalDateTimePanel
> doesn't show the scalar value.
> Partially the problem has been solved by moving
> {code}
> @javax.jdo.annotations.Persistent(defaultFetchGroup="true")
> {code}
> next to
> {code}
> @Column(allowsNull = "true")
> {code}
> applied on the property getters.
> But it appeared that the actual problem is that DataNucleus 3.x and 4.x do
> not support Joda-Time's LocalDateTime. There is support for Joda-Time's
> LocalDate and JSR310/ThreeTen/JDK8 LocalDateTime though.
> This ticket is to document the bug. Since there is no urgent need for
> supporting this type its priority is set to "Minor".
> Thanks to Dan for the directions!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
