Terracotta Discussion Forums

What I'm trying to do is build a servlet that uses a quartz to do job scheduling. The main thing that I'm having trouble with is how do I need to write my doPost method? I'm familiar with the idea of a jobstore that allows me to persist jobs. Should I simply create db entry's for the jobs that I want to run? How can I find my job details if this is what I do? Are there any "best practices" documents on this topic

Hello tam0009,

You typically would just use the Quartz API directly. See javadoc on org.quartz.Scheduler class. Also the quartz site has detail documentation on how to use Quartz properly. You shouldn't insert data by hand into data.

Also, there is a MySchedule project out there that runs as Servlet application. You may use that as your study example.

http://code.google.com/p/myschedule

Have fun!

Calling the scheduler directly doesn't really make sense in my case, but the servlet will have a running instance of a scheduler. My problem is how could I send all the the data associated with creating a job (job detail, trigger Info) to the servlet?

Quartz itself doesn't provide RESTful servlet, but only RMI and JMX for remoting. You would have to write the RESTful servlet that expose the scheduler; or google around might find other people have done similar.

Writing the servlet is the plan. Maybe I haven't been clear about that up to this point.

Basically, what I'm trying to do is have the servlet effectively work as a scheduler. The problem is I'm not yet sure how the format of the requests and the responses should be. For the request, I basically need to define a way to pass all the information associated w/ the job detail and the trigger, and for the response I'm not exactly sure how to respond if the client wanted to know say all the triggers for a job.

Is there a way to turn a jobdetail/trigger into a json?

a quartz rest agent is currently work in progress (there is already some code regarding this feature in trunk); we should be using jackson for exposing jobdetails and triggers in a json format.

I increased the timeout variable in the batch script.