[
https://issues.apache.org/jira/browse/CAMEL-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717633#comment-13717633
]
Zemian Deng commented on CAMEL-6067:
------------------------------------
Hi,
I would like help provide a patch for this feature.
To add this feature, we need to change the behavior when existing trigger is
detected when route is started. Currently it throws an exception unless Quartz
is configured in clustered mode. So this needs to be changed to update existing
trigger instead (just like clustered mode). Would anyone oppose to this?
Also as Vishal pointed out, there is no good reason to explicitly set
startTime() when endpoint is started for the trigger. It should be removed and
let Quartz calculate it. If we don't set one, Quartz will set to current date
as default anyway. Any repercussions for removing it that you can think of?
Zemian Deng
> Provider deleteJob=true|false as an option for Quartz component
> ---------------------------------------------------------------
>
> Key: CAMEL-6067
> URL: https://issues.apache.org/jira/browse/CAMEL-6067
> Project: Camel
> Issue Type: New Feature
> Components: camel-quartz
> Affects Versions: 2.10.2, 2.10.3
> Reporter: Vishal
> Priority: Minor
> Fix For: 2.12.0, Future
>
>
> Although there is an option for defining stateful jobs in the quartz
> component via stateful=true, the jobs created are eventually deleted when
> Camel shutsdown.
> Please see,
> http://camel.465427.n5.nabble.com/Quartz-triggers-being-deleted-when-shutting-down-Camel-tt5727257.html
> An option is needed to instruct Camel to not remove stateful jobs when coming
> down.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
