[
https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112090#comment-14112090
]
Charles Moulliard commented on CAMEL-7754:
------------------------------------------
For Quartz 1, we should improve the QuartzComponent class to add the
CamelProperty "QUARTZ_TRIGGER_CRON_TIMEZONE"
{code}
// enrich job data map with trigger information
if (cron != null) {
answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_TYPE,
"cron");
answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_CRON_EXPRESSION,
cron);
String timeZone =
EndpointHelper.resloveStringParameter(getCamelContext(),
(String)triggerParameters.get("timeZone"), String.class);
if (timeZone != null) {
answer.getJobDetail().getJobDataMap().put(QuartzConstants.QUARTZ_TRIGGER_CRON_TIMEZONE,
timeZone);
}
}
{code}
> Property Trigger.timerZone is declared as contant but not implemented
> ---------------------------------------------------------------------
>
> Key: CAMEL-7754
> URL: https://issues.apache.org/jira/browse/CAMEL-7754
> Project: Camel
> Issue Type: Bug
> Components: camel-quartz, camel-quartz2
> Affects Versions: 2.12.1, 2.13.2
> Reporter: Charles Moulliard
> Fix For: 2.14.0
>
>
> Seems that we have a problem with Quartz/Quartz2 components. The doc claims
> that we can setup this property in the URI "trigger.timeZone"
> (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz
> don't use it even if a constant is defined
> :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0
> We have the same issue too with quartz2 -->
> https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0
--
This message was sent by Atlassian JIRA
(v6.2#6252)
