[
https://issues.apache.org/jira/browse/ISIS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Koren updated ISIS-853:
------------------------------
Description:
creating and persisting an entity just containing a DateTime and a String
property via service action works just fine.
when this entity is reopened and saved in wicket viewer without changing
anything, the time component is set to 00:00.
or, to be more precise: to 00:00 UTC which, in my case, is rendered as 02:00
(vienna: UTC+1 + daylight saving time)
was:
creating and persisting an entity just containing a DateTime property via
service action works just fine.
when this entity is reopened and saved in wicket viewer without changing
anything, the time component is set to 00:00.
or, to be more precisely: to 00:00 UTC which is rendered as 02:00 in my case
(vienna, UTC+1 + daylight saving time)
i just found out, that this only happens if the DateTime property is marked
@Disabled.
without that annotation the correct value (including time component) is
persisted
> joda DateTime properties loose time when persisted
> --------------------------------------------------
>
> Key: ISIS-853
> URL: https://issues.apache.org/jira/browse/ISIS-853
> Project: Isis
> Issue Type: Bug
> Components: Core: Objectstore: JDO
> Affects Versions: objectstore-jdo-1.5.0
> Reporter: Thomas Koren
> Assignee: Dan Haywood
>
> creating and persisting an entity just containing a DateTime and a String
> property via service action works just fine.
> when this entity is reopened and saved in wicket viewer without changing
> anything, the time component is set to 00:00.
> or, to be more precise: to 00:00 UTC which, in my case, is rendered as 02:00
> (vienna: UTC+1 + daylight saving time)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
