You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ilia Naryzhny (JIRA)" <ji...@apache.org> on 2014/02/07 08:16:19 UTC
[jira] [Created] (WICKET-5501) Support of client timezones for
java.util.Date, java.util.Timestamp and etc.
Ilia Naryzhny created WICKET-5501:
-------------------------------------
Summary: 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
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.1.5#6160)