[
https://issues.apache.org/jira/browse/TRINIDAD-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson updated TRINIDAD-1920:
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.15-core
2.0.0.3-core
Status: Resolved (was: Patch Available)
> DateTimeRangevalidator fails across multiple timezones
> ------------------------------------------------------
>
> Key: TRINIDAD-1920
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1920
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.13-core
> Reporter: Yee-Wah Lee
> Priority: Minor
> Fix For: 2.0.0.3-core, 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.
> https://issues.apache.org/jira/browse/TRINIDAD-1818
> 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.
