[
https://issues.apache.org/jira/browse/OFBIZ-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892510#comment-16892510 ]
Nicolas Malin commented on OFBIZ-11035:
---------------------------------------
Two small remarks :
* don't create a xml element without node <field name="recurrenceTimeZone" type="id-long"></field> -> <field name="recurrenceTimeZone" type="id-long"/>
* Do you tried to always use a time zone ?
{code:java}
TimeZone timeZone = jobValue.get("recurrenceTimeZone") != null ? TimeZone.getTimeZone(jobValue.getString("recurrenceTimeZone") : TimeZone.getDefault();
next = expr.next(Calendar.getInstance(timeZone));
{code}
> Add timezone support to recurring job temporal expressions
> ----------------------------------------------------------
>
> Key: OFBIZ-11035
> URL:
https://issues.apache.org/jira/browse/OFBIZ-11035> Project: OFBiz
> Issue Type: Improvement
> Components: framework/webtools
> Affects Versions: Trunk
> Reporter: Pawan Verma
> Assignee: Pawan Verma
> Priority: Major
> Attachments: OFBIZ-11035.patch
>
>
> Link of the discussion: [
https://markmail.org/message/jsjqmjypaihbbldn]
> *As per Scott:*
> Trying to decide on the best way to define a *temporal* *expression* for a recurring job where the *temporal* *expression* should be evaluated using a *timezone* other than whatever the default *timezone* is for the system.
> The use case is having a system that runs on UTC time but needs to send a report at 5 pm Pacific Time every day regardless of whether or not daylight savings is in effect.
> Two options:
> # Add a field to *JobSandbox* such as recurrenceTimeZone (or better name!)
> # Use whatever *timezone* is available in the RunTime data service context
> Based on the discussion on Dev Mailing list #1 will be used to implement this feature.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
Locked
