[jira] Updated: (TRINIDAD-739) Timezone handling in trinidad-config.xml and ConvertDateTimeTag does not give notice on errors

["Yee-Wah Lee (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/TRINIDAD-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yee-Wah Lee updated TRINIDAD-739:
---------------------------------

    Status: Patch Available  (was: Open)

> Timezone handling in trinidad-config.xml and ConvertDateTimeTag does not give notice on errors
> ----------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-739
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-739
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.0.2-core
>            Reporter: Yee-Wah Lee
>            Priority: Minor
>
> In trinidad-config.xml, and in the DateTimeConverter tag, developers can specify the timezone using a ID string. If the timezone ID given does not match a supported timezone ID exactly (including case), the app behaves thus:
> E.g. If the user enters the wrong case for the timezoneID, such as. "america/new_york" instead of "America/New_York", the code would return the following: 
> Windows: Returns a ZoneInfo object with correct offsets, but ID = "america/new_york"
> Unix/Linux: Returns GMT TimeZone 
> No warning is given in the Unix/Linux case. For the Windows case, the ZoneInfo object is functional but developers must know to use case-insensitive comparison against other TimeZones. 
> Propose 'fixing' up the lookup by comparing it against one of the known timezones (available from TimeZone.getAvailableIDs()). And if the returned timezone doesn't match the input string, log a warning.

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