[jira] [Issue Comment Edited] (TAP5-841) DateField selects wrong date if client is in a different timezone than the server

["Matthew Dudley (JIRA)" <ji...@apache.org>]

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

Matthew Dudley edited comment on TAP5-841 at 9/2/11 2:18 PM:
-------------------------------------------------------------

Hi All,

I have tried Christophe Cordenier's fix for this issue. After I have modified my class and patched the datfield.js file with the code i get the following error:

org.apache.tapestry5.ioc.internal.OperationException: Error invoking constructor org.apache.tapestry5.internal.services.TemplateParserImpl(Map, boolean) (at TemplateParserImpl.java:50) via org.apache.tapestry5.internal.services.InternalModule.bind(ServiceBinder) (at InternalModule.java:65) (for service 'TemplateParser'): org/codehaus/stax2/XMLInputFactory2

Continued:
Caused by: java.lang.NoClassDefFoundError: org/codehaus/stax2/XMLInputFactory2

I have not changed anything relating to this error. Does anyone have any ideas?

Kind Regards

      was (Author: rtumatt):
    Hi All,

I have tried Christophe Cordenier's fix for this issue. After I have modified my class and patched the datfield.js file with the code i get the following error:
  
> DateField selects wrong date if client is in a different timezone than the server
> ---------------------------------------------------------------------------------
>
>                 Key: TAP5-841
>                 URL: https://issues.apache.org/jira/browse/TAP5-841
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: David Rees
>
> This affects 5.0.18 and 5.1.0.5 in my testing.
> Situation is that if the server is running in a different timezone than the client, the DateField chooser will select the wrong date on the calendar.
> For example, if the server is running in "Pacific/Auckland" and the client is running in "America/Los_Angeles", Auckland is a "day ahead" of Los Angeles for most of the time and the bug is easy to reproduce.
> Right now it is 3:40PM Sep 8, 2009 America/Los_Angeles and 10:40AM Sep 9, 2009 Pacific/Auckland.  If the date on the server to be displayed by the DateField is Sep 9, 2009, when you select the date chooser, Sep 8, 2009 is selected in the JavaScript calendar dialog.
> I found this message which seems to indicate that Howard thought it might be an issue - looks like he was correct:
> http://www.nabble.com/Re%3A-Tapestry-5.0.15-DateField-localization-problem--patch-included--p20033325.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira