Details
-
Feature
-
Status: Deferred (View Workflow)
-
Minor
-
Resolution: Unresolved
-
1.7
-
None
Description
Current Situation
- As stated in the article What time zone support is available in JobScheduler? the time_zone attribute is availabe for the element <schedule>.
- Currently, this attribute used in the <schedule> element has no effect.
Desired Behavior
- The time_zone attribute should be recognized by JobScheduler as it works in <run_time> element.
Further Explanations
- This works:
<?xml version="1.0" encoding="ISO-8859-1"?> <order> <run_time time_zone="Europe/London" schedule="europe_gtf_startup"/> </order>
<schedule> <weekdays > <day day="0"> <period single_start="19:00:00"/> </day> </weekdays> </schedule>
- This does not work:
<order> <run_time schedule="europe_gtf_startup"/> </order>
<schedule time_zone="Europe/London" > <weekdays > <day day="0"> <period single_start="19:00:00"/> </day> </weekdays> </schedule>
Maintainer Notes
- The documentation is wrong. An attribute <schedule time_zone="..."/> is not supported. The documentation has been fixed to reflect the effective behavior.
- There are use cases for an attribute <schedule time_zone="..."/>, e.g. not to have to specify the attribute for each job that makes use of the same schedule.
- Currently we estimate no immediate need to implement such behavior as the functionality is available by specifying <run_time schedule="..." time_zone="...".
- The respective functionality for adding time zones with the <run_time> element in JOE is covered by
JOE-155