title: Apache Camel-Quartz Integration
body: <p>I'm trying to use the <code>camel-quartz</code> Camel component to schedule jobs on our application server (this technology selection is final and is above my paygrade), and the only documentation Apache provides (<a href="http://camel.apache.org/quartz.html" rel="nofollow">here</a>) is de minimis and is ultra compacted without any real helpful examples for camel/quartz newbies.</p>
  
  <p>I'm trying to understand the big picture here, before I can drill down into my specific jobs' needs. The documentation states that - via Camel - Quartz timers are set up as endpoints. So I'm <strong>assuming</strong> (please correct me if I'm wrong) that this means that you code up jobs to be ran, along with their config/properties files, and then set up a Quartz timer as a Camel endpoint; then when those jobs get ran, they somehow can communicate over Camel to other endpoints (?).</p>
  
  <p><em>So is that the only benefit to using <code>camel-quartz</code> instead of just Quartz (that it allows your jobs to communicate with other endpoints)?</em></p>
  
  <p>Quartz can be configured with a <code>quartz.properties</code> file, and requires other configuration to so that a Scheduler can be initialized. <em>Does <code>camel-quartz</code> take care of this for you?</em> I'd like to just concentrate on writing the job, but not sure what sort of minimal XML or properties configurations are necessary.</p>
  
  <p>Thanks in advance to anyone who can help clarify this <code>camel-quartz</code> development process a little better.</p>