tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Gusev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-2494) CronSchedule timezone access
Date Fri, 28 Aug 2015 15:51:45 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720037#comment-14720037

Dmitry Gusev commented on TAP5-2494:

Make sure this is exactly what you need.

It's a best practice to run your JVM in a UTC timezone, then all timings become predictable.

Otherwise you're risking to get a timezone nightmare.

> CronSchedule timezone access
> ----------------------------
>                 Key: TAP5-2494
>                 URL: https://issues.apache.org/jira/browse/TAP5-2494
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-ioc
>    Affects Versions: 5.3.1, 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6, 5.3.7, 5.4, 5.3.8
>            Reporter: Volker Lamp
>              Labels: easyfix, patch
>         Attachments: TAP5-2494.patch
> CronSchedule can be instantiated with a cron expression string, but there is no way to
set a time zone. Specifically, the cron expression is not expected to contain time zone information;
there is neither a CronSchedule constructor with a TimeZone argument nor with a CronExpression
argument; and CronSchedule's CronExpression field is private.
> The proposed solution is to add a constructor that will accept a TimeZone argument. The
existing one-argument constructor would set the default time zone.

This message was sent by Atlassian JIRA

View raw message