Yeah, You can managed the quartz job your self by setting a quartz endpoint.
Here is the Junit test[1] which shows how to setup the job Trigger, you can also setup the the JobDetail there. [1] https://svn.apache.org/repos/asf/camel/trunk/components/camel-quartz/src/test/java/org/apache/camel/component/quartz/QuartzEndpointTest.java Willem Ryan Gardner wrote: >> On May 20, 2009, at 6:17 AM, Eric Bouer wrote: >> >>> >>> You guys are very helpful to others :) >>> So I guess I asked something wrong Or that there are no examples >>> anywhere. >>> In that case, Could you please demonstrate how to pass a job to quartz? >>> I'm using the so far well done 2.0-M1 >>> Eric. >>> >>> >>> >>> Eric Bouer wrote: >>>> >>>> Hello List. >>>> I'm new to camel and I looked over the Quartz component page in the >>>> documentation. >>>> I couldn't find any usefull example for using quartz jobs. >>>> I can see that I'm able to set job.name in the URI but >>>> I don't see where and how I can specify a job itself to a trigger. >>>> Are there any examples I should look for or some more camel-quartz >>>> documentation ? >>>> >>>> Thanks. >>>> Eric. >>>> >>>> > > I'm using quartz in my app but I'm not using the quartz endpoint - in > part because I don't know how to use it. > > I created a generic job that I store a message UID for a message > persisted elsewhere in my domain, a map of headers, and an endpoint URI. > When that job runs, I have it retrieve the datamap from the persistent > job, create a new message and then fire it off to the endpoint that was > stored on the job. > > It's simple, but it works for my case. > > I'm not sure if I could do all that using a quartz endpoint or not. In > my situation I have different kinds of jobs grouped in different groups > and sharing the same name (a uid) so I can cancel or reschedule all the > jobs associated with one unit of work at once. > > Perhaps the unit tests have examples of using the quartz endpoint? > > Ryan >
