[
https://issues.apache.org/jira/browse/WICKET-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911959#comment-13911959
]
Ilia Naryzhny commented on WICKET-5501:
---------------------------------------
I think that all Date related convertors should have common parent class with
ability to override getTimezone and getDateFormat methods. Currently, it's not
true and it's very hard to do with existing classes. And more over: as I can
see, there is no reason to use joda.time for this kind of convertions.
Joda.Time can just add some realizations for "extra" date formats.
Opinions of wicket's devs are very interesting...
> 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.1.5#6160)
