[
https://issues.apache.org/jira/browse/CAMEL-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735352#comment-13735352
]
Zemian Deng commented on CAMEL-6067:
------------------------------------
Claus,
The term "stateful" in Quartz does not mean retain trigger after stop
scheduler. It simply will re-persist the job data map between job run, and not
execute same job instance concurrently. If you change this usage/meaning in
camel, it will be very confusing for users.
As far as misfire concern, each trigger type in Quartz has their own misfire
mode, and they do just that: control whether to fast forward to now or even
just ignore it etc. If user wants different misfire policy than the one we set
then he/she can pre-create the trigger first and use the same name in the camel
URI.
To me, it doesn't make sense to reset/call startTime() if you were to retrieve
existing trigger.
> 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
>
> Attachments: CAMEL-6067.path
>
>
> 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
