[jira] [Commented] (ISIS-630) LocalDates are parsed to a wrong date when running in different timezone

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ISIS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847502#comment-13847502 ] 

ASF subversion and git services commented on ISIS-630:
------------------------------------------------------

Commit b87c2a9dcce23a0ede235584fa8ea493556081c9 in branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b87c2a9 ]

ISIS-630: fix parsing of joda LocalDate, and defaults in action prompt

Reworked implementation of JodaLocalDateValueSemanticsProvider, no longer converts to an underlying java.util.Date

Also, ensured that action prompt's args are cleared on cancel, so that defaults for action args are always obtained
if an action prompt dialog is shown, cancelled, then shown again.


> LocalDates are parsed to a wrong date when running in different timezone
> ------------------------------------------------------------------------
>
>                 Key: ISIS-630
>                 URL: https://issues.apache.org/jira/browse/ISIS-630
>             Project: Isis
>          Issue Type: Bug
>          Components: Viewer: Wicket
>    Affects Versions: viewer-wicket-1.3.1
>            Reporter: Jeroen van der Wal
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: viewer-wicket-1.4.0
>
>         Attachments: Screen Shot 2013-12-09 at 12.25.35 AM.png
>
>
> This issue occurred to me when doing some late night coding. It was around 12:30 AM CET when I ran an action which should have all date fields defaulted to 1-1-2014 but in return displayed as 31-12-2013. Setting my computer clock one hour ahead made the issue disappear. This could be critical in timezones further away from UTC.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)