[jira] [Commented] (ISIS-1132) possible timezone issues when refresh page in Wicket viewer.
[ https://issues.apache.org/jira/browse/ISIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314105#comment-15314105 ] ASF subversion and git services commented on ISIS-1132: --- Commit adcbcf8140a4ccc52e9ab46e4a31be4f17ac4aaa in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=adcbcf8 ] ISIS-1132: finally, the fix... the (legacy) Isis encoder/decoder stuff is used to copy the value from the object into the action parameter; the impl for joda DateTime was missing the time portion, so was defaulting to +1:00 (presumably due to locale, GMT+1 hour). > 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)
[jira] [Commented] (ISIS-1132) possible timezone issues when refresh page in Wicket viewer.
[ https://issues.apache.org/jira/browse/ISIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314103#comment-15314103 ] ASF subversion and git services commented on ISIS-1132: --- Commit eb90e2991de4355db481224d717a7c8de4ae688c in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=eb90e29 ] ISIS-1132: refactoring (no functional changes) ... rationalized and simplified the DataConverterForJoda hierarchy of classes. > 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)
[jira] [Commented] (ISIS-1132) possible timezone issues when refresh page in Wicket viewer.
[ https://issues.apache.org/jira/browse/ISIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314102#comment-15314102 ] ASF subversion and git services commented on ISIS-1132: --- Commit a2197cd52e2feac31bb54dec95193181ec058a36 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=a2197cd ] ISIS-1132: refactoring (no functional changes) in order to understand current design better. It seems that the datepicker pattern is not actually used; instead we read either the datePattern or the dateTimePattern and - if there is the picker for the component - then convert the format to moment.js format (as used by the bootstrap3 cpt we are using) on-the-fly. > 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)
[jira] [Commented] (ISIS-1132) possible timezone issues when refresh page in Wicket viewer.
[ https://issues.apache.org/jira/browse/ISIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314101#comment-15314101 ] ASF subversion and git services commented on ISIS-1132: --- Commit 1dd64e618aebb85669ac8ceeed8deefc89c25c34 in isis's branch refs/heads/maintenance-1.12.x from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=1dd64e6 ] ISIS-1132: finally, the fix... the (legacy) Isis encoder/decoder stuff is used to copy the value from the object into the action parameter; the impl for joda DateTime was missing the time portion, so was defaulting to +1:00 (presumably due to locale, GMT+1 hour). > 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)
[jira] [Commented] (ISIS-1132) possible timezone issues when refresh page in Wicket viewer.
[ https://issues.apache.org/jira/browse/ISIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (ISIS-1132) possible timezone issues when refresh page in Wicket viewer.
[ https://issues.apache.org/jira/browse/ISIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314107#comment-15314107 ] ASF subversion and git services commented on ISIS-1132: --- Commit 1dd64e618aebb85669ac8ceeed8deefc89c25c34 in isis's branch refs/heads/master from [~danhaywood] [ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=1dd64e6 ] ISIS-1132: finally, the fix... the (legacy) Isis encoder/decoder stuff is used to copy the value from the object into the action parameter; the impl for joda DateTime was missing the time portion, so was defaulting to +1:00 (presumably due to locale, GMT+1 hour). > 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)
