[jira] [Closed] (ISIS-1015) [WON'T FIX] DataNucleus doesn't support LocalDateTime

["Dan Haywood (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ISIS-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood closed ISIS-1015.
-----------------------------
    Resolution: Won't Fix

Some commits have been made on this, but I'm gonna mark it as "WON'T FIX" ... it can't be a major issue because this ticket is 3 years old...

> [WON'T FIX] 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: 2.0.0-M2
>
>
> 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
(v7.6.3#76005)