[CAMEL-4197] scheduled route policy should not start Quartz scheduler, but let QuartzComponent do that

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.8.0
• Component/s: camel-quartz
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 08/Jul/11 13:20
• Updated: 08/Jul/11 13:21
• Resolved: 08/Jul/11 13:21

Description

The QuartzScheduler lifecycle is handled by QuartzComponent and we should let it startup the scheduler. The component does this best as it has logic to ensure all that the scheduler is only started after the entire CamelContext has been fully initialized and started. This is to ensure the scheduler do not trigger any action that may send in messages to Camel routes and whatnot too early (when CamelContext is not really ready).