[
https://issues.apache.org/jira/browse/TRINIDAD-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720783#action_12720783
]
Yee-Wah Lee commented on TRINIDAD-1512:
---------------------------------------
The zone.setID(..) code seems to be done because of performance reasons. If
the date time converter supported full strings in the timezone display, it
would have to send down the translations for the possible timezone names, e.g.
"EDT", "PST" and "Eastern Daylight Time", "Pacific Standard Time".
Even if taking the commonly used timezones (300+ out of possible 500+), that
would add substantial size since the locale file data would serve all
converters on the page, and some could have timeStyle="full", some would have
timeStyle="long" hence it would need to contain all formatting variants of the
timezone name.
> ConvertDateTime uses static GMT+x string for timezone display, doesn't update
> for daylight savings
> --------------------------------------------------------------------------------------------------
>
> Key: TRINIDAD-1512
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1512
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.11-core
> Reporter: Yee-Wah Lee
> Priority: Minor
>
> 1. Create a jsp that uses tr:convertDateTime to display timezone, e.g.
> <af:outputText value="#{demoInput.date}">
> <af:convertDateTime type="both" timeStyle="full"
> timeZone="America/New_York"/>
> </af:outputText>
> where demoInput.date returns the current date, e.g. June 17 09, 1:00 PM
> 2. Run the jsp. For June 17 09 the timezone is actually EDT (GMT - 4).
> Instead it displays as EST
> 6/17/2009 1:00:00 PM GMT-05:00
> If using the JSF standard DateTimeConverter, the output is:
> Jun 17, 2009 1:00:00 PM EDT
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
