You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Peter Mahoney (JIRA)" <de...@myfaces.apache.org> on 2007/06/21 15:15:26 UTC

[jira] Updated: (TOMAHAWK-811) Have the 'schedule' component deal with timezones

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

Peter Mahoney updated TOMAHAWK-811:
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.7-SNAPSHOT
           Status: Resolved  (was: Patch Available)

This has been commited. In the end the timezone was added to the model, as per the patch, as adding it to the UIScheduleBase would have coupled the model to the component unnecessarily.

> Have the 'schedule' component deal with timezones
> -------------------------------------------------
>
>                 Key: TOMAHAWK-811
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-811
>             Project: MyFaces Tomahawk
>          Issue Type: Improvement
>          Components: Schedule
>    Affects Versions: 1.1.5-SNAPSHOT
>            Reporter: Eduard Martinescu
>            Assignee: Peter Mahoney
>             Fix For: 1.1.7-SNAPSHOT
>
>         Attachments: schedule.timezone.patch
>
>
> Currently, the schedule component makes all calculations in the default timezone of the server. However, it is desirable to display schedules in alternate timezones.  For example, I have an app that runs in EST5EDT, but the users want all scheduling to occur in GMT.

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