[ https://issues.apache.org/jira/browse/ISIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314104#comment-15314104 ]
ASF subversion and git services commented on ISIS-1132: ------------------------------------------------------- Commit b332a8bd9e3c5a7ccd16ecccbb3e14342b6d04c2 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=b332a8b ] ISIS-1132: further refactoring (no functional change) - showing how the bootstrap datetime config is built from the converter's dateTime pattern. > possible timezone issues when refresh page in Wicket viewer. > ------------------------------------------------------------ > > Key: ISIS-1132 > URL: https://issues.apache.org/jira/browse/ISIS-1132 > Project: Isis > Issue Type: Bug > Components: Core: Viewer: Wicket > Affects Versions: core-1.8.0 > Reporter: Boris Toninski > Assignee: Dan Haywood > Fix For: 1.12.2 > > > The issue is reproducible in the latest kitchensink demo application which > uses Isis 1.8.0. > When a form page is opened and the URL in the browser is like - > ".../wicket/entity?15" and the page is refreshed, following happens: > - All "org.joda.time.DateTime" fields are changed, so they have "03:00" at > the end. (ex. It was ...00:00 and becomes ...03:00) > - The splitters in the menus disappear. > I suppose there can be some other issues too. > The URL becomes like ".../wicket/entity?15" after a form is edited or if you > click for example on the "First DateObject" menu item in kitchensink app. If > the URL is like ".../wicket/entity/DATE:L_0" it works normally. -- This message was sent by Atlassian JIRA (v6.3.4#6332)