...
| Div |
|---|
| class | confluenceTableSmall |
|---|
|
Parameter | Default | Description |
|---|
cron
| None | Specifies a cron expression (not compatible with the trigger.* or job.* options). | trigger.repeatCount
| 0
| SimpleTrigger: How many times should the timer repeat? | trigger.repeatInterval
| 1000
| SimpleTrigger: The amount of time in milliseconds between repeated triggers. Must enable trigger.repeatCount to use the simple trigger using this interval. | job.name
| null
| Sets the job name. | job.XXX
| null
| Sets the job option with the XXX setter name. | trigger.XXX
| null
| Sets the trigger option with the XXX setter name. | stateful
| false
| Uses a Quartz @PersistJobDataAfterExecution and @DisallowConcurrentExecution instead of the default job. | fireNow
| false
| If it is true will fire the trigger when the route is start when using SimpleTrigger. | deleteJob
| true
| If set to true, then the trigger automatically delete when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true. | pauseJob
| false
| If set to true, then the trigger automatically pauses when route stop. Else if set to false, it will remain in scheduler. When set to false, it will also mean user may reuse pre-configured trigger with camel Uri. Just ensure the names match. Notice you cannot have both deleteJob and pauseJob set to true. | durableJob
| false
| Camel 2.12.4/2.13: Whether or not the job should remain stored after it is orphaned (no triggers point to it). | recoverableJob
| false
| Camel 2.12.4/2.13: Instructs the scheduler whether or not the job should be re-executed if a 'recovery' or 'fail-over' situation is
encountered. | usingFixedCamelContextName | false | Camel 2.15.0: If it is true, JobDataMap uses the CamelContext name directly to reference the camel context, if it is false, JobDataMap uses use the CamelContext management name which could be changed during the deploy time. |
|
For example, the following routing rule will fire two timer events to the mock:results endpoint:
...
