Uploaded image for project: 'MyFaces Trinidad'
  1. MyFaces Trinidad
  2. TRINIDAD-1920

DateTimeRangevalidator fails across multiple timezones

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.2.13-core
    • 1.2.14-core , 2.0.0-beta-1
    • Components
    • None

    Description

      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.

      Attachments

        1. 12123_1920.diff
          10 kB
          Yee-Wah Lee
        2. 12x_1920.diff
          6 kB
          Yee-Wah Lee
        3. trin12_1920.diff
          12 kB
          Yee-Wah Lee

        Activity

          People

            Unassigned Unassigned
            yeelee Yee-Wah Lee
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: