[
https://issues.apache.org/jira/browse/ISIS-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-392:
-----------------------------
Description:
This JIRA is to bring a bit of consistency to the implementation.
One particular improvement is that joda LocalDate is no longer converted to a
java.util.Date internally (which might lead to timezone issues).
Another improvement is to use the same dateformat when rendered in compact form
(as in tables) as in the regular form (as in property form).
A final improvement is to make the datepicker honour the specified
datePattern/dateTimePatterns. This is a stepping stone to making this
configurable externally (either application-level, or per-user).
There are still some issues, even with this JIRA tackled. In particular,
handling of date/time values doesn't work obviously for non-UTC timezones if
specified with a truncated date. Not sure what the solution is here, other
than to (perhaps) require that a time is always specified.
was:
This JIRA is to bring a bit of consistency to the implementation. One
particular improvement is that joda LocalDate is no longer converted to a
java.util.Date internally (which might lead to timezone issues).
There are still some issues, even with this JIRA tackled. In particular,
handling of date/time values doesn't work obviously for non-UTC timezones if
specified with a truncated date. Not sure what the solution is here, other
than to (perhaps) require that a time is always specified.
> In Wicket, provide a datepicker for all of the date/datetime value types.
> -------------------------------------------------------------------------
>
> Key: ISIS-392
> URL: https://issues.apache.org/jira/browse/ISIS-392
> Project: Isis
> Issue Type: Improvement
> Components: Viewer: Wicket
> Affects Versions: viewer-wicket-1.1.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: viewer-wicket-1.2.0
>
>
> This JIRA is to bring a bit of consistency to the implementation.
> One particular improvement is that joda LocalDate is no longer converted to a
> java.util.Date internally (which might lead to timezone issues).
> Another improvement is to use the same dateformat when rendered in compact
> form (as in tables) as in the regular form (as in property form).
> A final improvement is to make the datepicker honour the specified
> datePattern/dateTimePatterns. This is a stepping stone to making this
> configurable externally (either application-level, or per-user).
> There are still some issues, even with this JIRA tackled. In particular,
> handling of date/time values doesn't work obviously for non-UTC timezones if
> specified with a truncated date. Not sure what the solution is here, other
> than to (perhaps) require that a time is always specified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
