[
https://issues.apache.org/jira/browse/WICKET-5877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492391#comment-14492391
]
Ulrich Schmidt edited comment on WICKET-5877 at 4/13/15 1:32 PM:
-----------------------------------------------------------------
Is there any docu available. As I stated in my problem ticket, I'm a newbie
with wicket. It's quite annoying having a method getDate() an getModelObject()
which both are supposed to provide a Date and both delivering different
results. I would like to understand whats going on here.
This is especially necessary as the both of my programs seem to provide
different results for DateTimeField.getDate(). So I'm kind of worried whether I
can supply a stable program.
was (Author: u005078):
Is there any docu available. As I stated in my problem ticket, I'm a newbie
with wicket. It's quite annoying having a method getDate() an getModelObject()
which both are supposed to provide a Date and both delivering different
results. I would like to understand whats going on here.
> DateTimeField changes not getting effective without page refresh
> ----------------------------------------------------------------
>
> Key: WICKET-5877
> URL: https://issues.apache.org/jira/browse/WICKET-5877
> Project: Wicket
> Issue Type: Bug
> Components: wicket-datetime
> Affects Versions: 1.4.20, 6.19.0
> Reporter: Ulrich Schmidt
> Assignee: Sven Meier
> Priority: Minor
> Attachments: HomePage.html, HomePage.html, HomePage.java,
> HomePage.java
>
>
> DateTimeFields displays a date, a date-selection icon and time in form hh:mm.
> If one just edits the hour or minute and press a button right away where the
> "onSubmit"-method displays the entered valut to log, the LOGGER shows the
> resulting timestamp as if it wasn't changed.
> Editing the time only becomes effective if you refresh the page by pressing
> "F5" or select the date-selection icon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
