myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yee-Wah Lee (JIRA)" <>
Subject [jira] Commented: (TRINIDAD-1920) DateTimeRangevalidator fails across multiple timezones
Date Thu, 02 Dec 2010 22:12:11 GMT


Yee-Wah Lee commented on TRINIDAD-1920:

See Trinidad-1967 for an update of this fix.

> DateTimeRangevalidator fails across multiple timezones
> ------------------------------------------------------
>                 Key: TRINIDAD-1920
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.2.13-core 
>            Reporter: Yee-Wah Lee
>            Priority: Minor
>             Fix For:,  1.2.15-core 
>         Attachments: 12123_1920.diff, 12x_1920.diff, trin12_1920.diff
> This is a regression from TRINIDAD-1818 where the DateTimeRangeValidator was created
with Date/ms. 
> Because the Javascript client is not able to correctly calculate timezone offsets for
different timezones, it should take the min/max as a String and convert that into a Date.
The converted value would have the same offset as the value, and validation would be all on
objects with the same timezone offset. 
> Fix is to revert to using Strings, but also pass the date as an ISO string when the converter
pattern is insufficient. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message