[jira] [Resolved] (WICKET-5501) Support of client timezones for java.util.Date, java.util.Timestamp and etc.

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-5501.
-------------------------------------

    Resolution: Won't Fix

Closing as "Won't fix".
If we add overridable #getTimeZone() then the application code will have to extend the class to set the needed time zone. It is the same now - the class has to be extended, override #getDateFormat() and set the timezone.

> Support of client timezones for java.util.Date, java.util.Timestamp and etc.
> ----------------------------------------------------------------------------
>
>                 Key: WICKET-5501
>                 URL: https://issues.apache.org/jira/browse/WICKET-5501
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket, wicket-datetime
>    Affects Versions: 6.13.0
>            Reporter: Ilia Naryzhny
>              Labels: converter, time_zone, wicket
>         Attachments: AbstractDateConverter.java
>
>
> That was surprise for me that wicket doesn't support convertion of java.util.Date, java.sql.Date, java.sql.Time, java.sql.Timestamp taking into account client timezone.
> I know about existing DateConverter/StyleDateConverter and etc. But it's not so easy to extend and reuse that for java.sql.* types.
> Please find in the attachment our implementation of date convertor which is taking into account client timezone and (!) don't use org.joda.time. Hope that it can be included (maybe after some refactoring) into main branch. Please let me know your vision of this approach and if you are OK: let me go ahead and prepare patch. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)