[
https://issues.apache.org/jira/browse/TAP5-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720060#comment-14720060
]
Volker Lamp commented on TAP5-2494:
-----------------------------------
I know, working with time zones can be tricky. Actually the host, and my JVM
for that matter, run in UTC. However, instantiating CronSchedule with a
TimeZone saves me from translating my desired trigger times (which are time
zone dependent) back to UTC.
My patch does not change the previous behavior. It just adds a little bit of
flexibility for anyone needing to specifically set a time zone.
> 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
(v6.3.4#6332)
